Ratpack, a high performance Java web framework, has reached 1.0 status. The 1.0 release is API-stable and can be considered production ready. The main thing that makes Ratpack interesting is the execution model, which aims to make asynchronous programming on the JVM easier.
During the second technical keynote at SpringOne2GX last week Guillaume Laforge talked about plans for Groovy 2.4.x and 2.5. Perhaps the most significant is improved compiler performance with a new Abstract Syntax Tree (AST) class reader in place of using class loading tricks.
This post covers scrum myths described by Ilan Goldstein, Certified Scrum Trainer.
Typesafe's Play team has released version 2.4 "Damiya" of their web framework. By embracing dependency injection, the refactoring towards better modularization that was started in 2.3 has continued in this release. Play 2.4 requires Java 8 and uses Lambdas and Default Methods in Play's Java-API.
The Grails team released Grails 3.0, a complete rewrite of the popular MVC framework now based on Spring Boot. Grails 3.0 contains a number of new features including Groovy 2.4 and Android support, Spring 4.1, and Gradle replacing the old Gant-build system.
In response to cloud vendor Pivotal pulling support for the Groovy/Grails project, Groovy head Guillaume Laforge has joined open source API platform Restlet to lead API development tools. InfoQ spoke to Laforge about Restlet, Groovy, and his new responsibilities.
Pivotal Software today announced that it will be withdrawing funding for the popular Groovy and Grails frameworks after March 31, 2015. Pivotal cited their larger strategy to concentrate resources on accelerating both commercial and open source projects that support its growing traction in Platform-as-a-Service, Data, and Agile development.
Garrick Toubassi, Google Inbox engineering director, has recently explained how his team could get to "sharing roughly two-thirds of their client code" across three platforms: iOS, Android, and the web. The key is a clear separation of concerns between UI code and UI-independent logic, and a couple of tools that Google developed through the years.
There are different opinions for conducting sprint planning. Long debate is happening between velocity driven sprint planning and commitment driven sprint planning. Mike Cohn, founder of Mountain Goat Software, shared his views in his recent blog on Why I Prefer Commitment-Driven Sprint Planning.
Oracle recently announced a JSR for MVC 1.0. JSR 371 was motivated by results of a Java EE 8 Survey, covered by InfoQ in March of this year. 61% of those surveyed supported the idea of providing support for an action-based MVC framework, alongside JSF. Only 26% felt there was an existing framework that could do the job, and 42% of those mentioned Spring MVC.
Agile software development teams have to assure that the products that they develop have sufficient quality. Management often also expect that they increase their velocity to be able to deliver more functionality faster to their customer. Several authors explored the relationship between quality and velocity and suggested ways to improve both quality and velocity.
The Play 2.3 release increases modularization of the framework by separating parts from the framework. Also, the Play shell has been replaced by Activator, which includes a browser UI and project templates. InfoQ also talked to Play tech lead James Roper to learn more about the changes and futures plans.
The latest release of PrimeTek's PrimeFaces 5.0 adds a new charting API, new components, rewritten mobile support, a new exception handler and improved push features. Nicknamed PF5, the release is compatible with JavaServer Faces 2.0 and greater. PrimeFaces Mobile (PFM) has been rewritten from scratch and is now included in the core distribution. PFM is built on jQuery Mobile.
TechEmpower has been running benchmarks for the last year, attempting to measure and compare the performance of web frameworks. For these benchmarks the term “framework” is used loosely including platforms and micro-frameworks.
Agile teams measure the velocity of their sprints. It helps them to plan and track their progress and provides insight for product owners to plan product releases. Can teams also use velocity data when they want to improve themselves? Several authors have written about velocity and shared their concerns on measuring velocity to improve the productivity of teams.