Skip to main content

Home/ Arquitectura?/ Group items tagged language

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Pablo Lalloni

Slick - Scala Language Integrated Connection Kit - Slick 1.0.0 documentation - 0 views

slick.typesafe.com/1.0.0

slick scalaquery data-access reference scala library documentation

shared by Pablo Lalloni on 18 Feb 13 - No Cached
  • Pablo Lalloni on 18 Feb 13
     
    Documentación de referencia de SLICK 1.0.0 (ex scalaquery) recientemente liberado. Pegarle una mirada.
Pablo Lalloni

The Jargon File - 0 views

www.catb.org/...index.html

geek jargon language culture hacker-culture

shared by Pablo Lalloni on 24 Oct 12 - Cached
  • Pablo Lalloni on 24 Oct 12
     
    Fuente de iluminación imprescindible para comprender nuestro mundo y a nosotros mismos.
carlosmiranda

TIOBE Software: Tiobe Index - 3 views

www.tiobe.com/...index.html

language development articles

shared by carlosmiranda on 14 May 12 - Cached
  • carlosmiranda on 14 May 12
     
    Interesante lo de C
Pablo Lalloni

Atomic Scala | Learn Programming in a Language of the Future - 0 views

www.atomicscala.com

programming scala development learning

shared by Pablo Lalloni on 17 Sep 12 - No Cached
  • Pablo Lalloni on 20 Sep 12
     
    Cartón lleno... Bruce Eckel se subió al vagón de scala...
Sebastián Zaffarano

Adobe donates Flex to Apache - Web services development, software, open source, Languag... - 4 views

www.techworld.com.au/...adobe_donates_flex_apache

shared by Sebastián Zaffarano on 17 Nov 11 - No Cached
  • Sebastián Zaffarano on 17 Nov 11
     
    Mucho por decir no hay.... "Adobe also suggested that Web application developers in the future would be using HTML5 rather than Flash."
  • Pablo Lalloni on 18 Nov 11
     
    Otro approach mas generador de oportunidades para la empresa podría haber sido sumar al SDK un compilador que produzca html5 en lugar de flash. Y sin duda mucho mejor recibido por todos sus clientes actuales y por todos los que vienen invirtiendo en flex!
Pablo Lalloni

Who is the Go Developer? - The New Stack - 1 views

thenewstack.io/who-is-the-go-developer

development programming golang it-industry industry careers technology career programming-languages

shared by Pablo Lalloni on 06 Jul 15 - No Cached
  • Pablo Lalloni on 06 Jul 15
     
    Muy buena mirada al estado del mercado de Go.
Pablo Lalloni

Unirest - Simplified, lightweight HTTP request client libraries in multiple languages - 1 views

unirest.io

http rest development programming libraries java python node .net ruby

shared by Pablo Lalloni on 07 Jul 15 - No Cached
  • Pablo Lalloni on 07 Jul 15
     
    ¡Muy buenas!
Pablo Lalloni

Dart : Structured web programming - 0 views

www.dartlang.org

programming languages development dart

shared by Pablo Lalloni on 01 Nov 11 - No Cached
  • Pablo Lalloni on 01 Nov 11
     
    Google publicó el primer preview de su nuevo lenguaje. Soporta 2 ambientes de ejecución: una nueva virtual machine y compilado a javascript. La VM soporta startups muy rápidos leyendo el estado del sistema desde archivos de imagen estilo smalltalk. El lenguaje es OO pero basado en interfaces, no clases (aunque tiene clases, todos los method dispatch se refieren a una interfaz). El tipado estático es 100% opcional, permite no poner tipos e incluso permite ejecutar código que no valide el typechecker (con errores). El modelo de ejecución es tipo erlang como procesos single-threaded aislados unos de otros (no pueden compartir nada) que solo se comunican pasando mensajes, éstos se llaman "Isolates".
Pablo Lalloni

Microservices and PaaS - Part I | ActiveState - 0 views

www.activestate.com/...microservices-and-paas-part-i

development programming cloud-computing microservices architecture software-architecture software-engineering

shared by Pablo Lalloni on 25 Aug 14 - No Cached
  • Instead of building software that resembles our existing organizations, we should figure out how we want our software to look, then build the organization around that. Or reorganize it if it's already in place.
    • Pablo Lalloni
      Pablo Lalloni on 25 Aug 14
       
      Las implicancias de esta idea en nuestra organización...
  • When deploying a new feature, enhancing or fixing an existing capability, or deploying an experimental line of code, the previous code remains available and accessible. New code is deployed alongside the old code, with mechanisms in place to instantly route to one or another version.
  • Importantly, the old code is not replaced, but remains part of the system, and is kept running. If, as is often the case, the widespread introduction of the new feature results in unforeseen consequences, the feature flag can be toggled off, and the old version is instantly used instead.
  • ...13 more annotations...
  • In a microservices architecture, an application is comprised of a number of small, independent composable services that interact by way of an external published protocol, such as REST, or a messaging service.
  • Each service is focused on an individual targeted business capability, and thus its scope is minimized. For functionality out of scope, the microservice calls out to other microservices via the published protocol.
  • Small independent microservices can be built using the technology best suited for their requirements. No longer does every application component need to be built on a common company-mandated language and framework such as Java/Spring or Ruby on Rails.
  • Similarly, there's no reason to standardize on a single persistence layer across an entire application. Some microservices might best be served by Redis, others by Oracle.
  • Each microservice can be updated independently, no longer requiring the entire application to be redeployed.
  • Microservices drastically improve the time required to push out a new update, allowing a much more agile development process.
  • Many organizations consist of specialized silo teams (UI, database, API, etc) where costly handoffs and intercommunication are required to coordinate all the pieces of application construction. These handoffs cause overhead, and the need for them should be eliminated.
  • With small teams, each focused on an individual microservice, Netflix enables developers to push code to production, instead of getting mired in a complex deployment process involving several teams.
  • With microservices, the old IT mindset just doesn't work.
  • A centralized IT department cannot possibly cover the wide array of technologies spanning all microservices.
  • Instead a DevOps structure, where each team is responsible for the management of the corresponding microservice, is essential.
  • Enable developers to concoct systems of their choosing with minimal or no interaction from IT, management, VPs, hardware or other groups. "Self Service" is one of the major capabilities offered by the cloud and there's every reason to take advantage of this.
  • Now, IT can be considered as a cloud API available to the developer on-demand 24x7, instead of a complex, process-mired division hidden behind obscure process.
Pablo Lalloni

PHP: a fractal of bad design / fuzzy notepad - 2 views

eev.ee/...php-a-fractal-of-bad-design

development programming php programming-languages

shared by Pablo Lalloni on 12 Jul 14 - No Cached
  • Pablo Lalloni on 12 Jul 14
     
    Este artículo sobre PHP es sumamente hilarante...
Pablo Lalloni

Scala.js no longer experimental | The Scala Programming Language - 1 views

scala-lang.org/...js-no-longer-experimental.html

scala programming development web-development javascript tools

shared by Pablo Lalloni on 10 Feb 15 - No Cached
    • Pablo Lalloni
      Pablo Lalloni on 10 Feb 15
       
      Uuuuhuuuu!
  • Pablo Lalloni on 10 Feb 15
     
    "Today, we announced the release of Scala.js v0.6.0, the Scala to JavaScript compiler, and dropped the experimental flag associated to it. Yes, you read it right: Scala.js is no longer experimental! After exactly 2 years of development, we finally feel comfortable calling it production-ready."
« First ‹ Previous 61 - 79 of 79
Showing 20▼ items per page