Group items tagged

"A Go web development eco-system, designed to make the life of a Go web developer easier."

"Introduction In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps that: Use declarative formats for setup automation, to minimize time and cost for new developers joining the project; Have a clean contract with the underlying operating system, offering maximum portability between execution environments; Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration; Minimize divergence between development and production, enabling continuous deployment for maximum agility; And can scale up without significant changes to tooling, architecture, or development practices. The twelve-factor methodology can be applied to apps written in any programming language, and which use any combination of backing services (database, queue, memory cache, etc). Background The contributors to this document have been directly involved in the development and deployment of hundreds of apps, and indirectly witnessed the development, operation, and scaling of hundreds of thousands of apps via our work on the Heroku platform. This document synthesizes all of our experience and observations on a wide variety of software-as-a-service apps in the wild. It is a triangulation on ideal practices for app development, paying particular attention to the dynamics of the organic growth of an app over time, the dynamics of collaboration between developers working on the app's codebase, and avoiding the cost of software erosion. Our motivation is to raise awareness of some systemic problems we've seen in modern application development, to provide a shared vocabulary for discussing those problems, and to offer a set of broad conceptual solutions to those problems with accompanying terminology. The format is inspired by Martin Fowler's books Patterns of Enterprise Application Architecture and Refactoring. Who should

Bueno. Eso. Compartí el que me di cuenta que puso antes Pablo en vez del original por error, pero la idea entre ambos, si la obviedad es tolerable, es idéntica :) Está muy bien estructurado en cuanto que cada factor depende de los demás a la vez que los promueve. Permite un enfoque general que incluye prácticas de arquitectura - y de armado cotidiano de productos - que posibilitan llegar donde yo entiendo - según me voy enterando - que es el lugar a donde llegar. Sin embargo, creo que ni éste departamento en sus sistemas más nuevos cumple todos y cada uno de aquellos factores. Esto, lejos de ser una crítica, es una invitación para que revisemos si es el único método posible - cosa improbabilísima - o el mejor método - también bastante improblable - a seguir. Lo que sí sostengo como un absoluto - quien no lo haría - es que es un método practicable. Mi aporte mínimo es defenderlo como uno bueno.

"Web Components usher in a new era of web development based on encapsulated and interoperable custom elements that extend HTML itself. Built atop these new standards, Polymer makes it easier and faster to create anything from a button to a complete application across desktop, mobile, and beyond."

Reactive-web is a new framework for writing highly interactive and dynamic web applications. It's written in Scala , sits on top of Lift, and uses the Functional Reactive Programming library reactive-core (it's in the same repository). As in GWT, you can code the user interface in the same language as the rest of your application (except in Scala instead of Java), rather than writing JavaScript. Unlike GWT, however, you don't need an extra build step to convert your code to JavaScript. You can easily combine code that runs on the browser with code that runs on the server. And, you can declare dynamic relationships between components, like binding in Flex/JavaFX/etc. (only much more powerful).

"But when Mark Russinovich, Microsoft's CTO for Azure, took the stage at Build 2015 in San Francisco Wednesday morning to demonstrate how containerized microservices applications work in Windows Server. [...] As is his wont, he dove right in to a demonstration of using Docker Build (on a PowerShell command line) to package and deploy an ASP.NET web site as a Docker container. [...] He took only a few seconds to package the web site into a container image, then he ran the package with the docker run command. [...] And then he paused, took the temperature of the room, and may have recognized that Windows developers may have been completely confused by what they were seeing. [...] So Russinovich asked for a show of hands of folks in the room who might have heard of something called Linux. (Don't worry, he's done this before.) [...] He then used a new build of Visual Studio, running in Windows, to publish the container to the Linux host. He then proceeded to debug the running Linux app, including setting a remote breakpoint, from Visual Studio. [...] Without saying so explicitly, Mark Russinovich was obsoleting much of Windows Server before developers' eyes."

"At the end of the series, you will understand not only the best practices of web development in Go but you will also know about different solutions for each problem a framework solves and be able to apply the right solution for each project."

"This document contains current data regarding the (Publication) Status of specifications being developed by the Web Applications Working Group (aka WebApps). The data is provided in several tables: 1) API Specifications; 2) Web Components Specifications; 3) Widget Specifications; 4) Recommendations in Maintenance Mode; and 5) Specs NO Longer Active."

Data.js is a data representation framework for Javascript. It is being developed in the context of Substance, a web-based document authoring and publishing engine. It took some inspiration from various existing libraries such as the Google Visualization API or Underscore.js.  You can report bugs and discuss features on the GitHub issues page, on Freenode IRC in the #_substance chann el, post questions to the Google Group, or send tweets to @_substance. With Data.js you can: Model your domain data using a simple graph-based object model that can be serialized to JSON. Traverse your graph, including relationships using a simple API. Manipulate and query data on the client (browser) or on the server (Node.js) by using exactly the same API. 

Dropwizard is a Java framework for developing ops-friendly, high-performance, RESTful web services. Dropwizard has out-of-the-box support for sophisticated configuration, application metrics, logging, operational tools, and much more, allowing you and your team to ship a production-quality HTTP+JSON web service in the shortest time possible.

MockFlow es una herramienta web para crear mocks de UIX de aplicaciones web, android, windows phone, ios, etc.

"Apache Rave a new web and social mashup engine that aggregates and serves web widgets. Rave is targeted as engine for internet and intranet portals and integrates Apache Shindig & Apache Wookie to provide OpenSocial & W3C widget support, respectively."

"A high-productivity web framework for the Go language."

"This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field."

Mucho por decir no hay.... "Adobe also suggested that Web application developers in the future would be using HTML5 rather than Flash."

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!

"Postman on Chrome is the most efficient way to test, develop and document APIs. Create complex requests, go back in time and view results in a beautiful way. Postman has more than 80 features to help you at every step."

"An open source framework to build and develop your applications in the Go way."

"Batman.js is a framework for building rich web applications with CoffeeScript or JavaScript. App code is concise and declarative, thanks to a powerful system of view bindings and observable properties. The API is designed with developer and designer happiness as its first priority."

"Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services."