InfoQ's research initiative continues with a 15th question about: "Ruby On Rails State of Practice: Deployment and Management". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.
Twitter's infamous Fail Whale was absent on US presidential election day, even as Twitter's servers were handling a serge of 327,452 "tweets" per minute. The firm was able to handle this level of traffic thanks in part to a gradual shift away from Ruby to Java and Scala
Ruby 2.0's release manager Yusuke Endoh announced the first preview release of Ruby 2.0 and a targeted release in February 2013. InfoQ talked to Yusuke to learn more about the big new features of Ruby 2.0 (Refinements, keyword arguments, Enumerator#lazy, and more) and what users need to know when upgrading.
As part of InfoQ's ongoing Community Driven Research project, we want to find out how developers are using Ruby on Rails in practice. In this first step, we want to know what you use so that we can collect suggestions for the voting.
InfoQ's research initiative continues with an 10th question: "Top 20 Web Frameworks for the JVM". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.
LinkedIn replaced their back-end mobile infrastructure built on Ruby on Rails with Node.js some time ago for performance and scalability reasons. A former LinkedIn team member reacted explaining what went wrong, in his opinion.
The upcoming Ruby on Rails 4.0 release will drop support for Ruby 1.8 and comes with many new features. The most important ones are support for strong parameters for mass-assignment protection, a new queue for background tasks, and caching improvements.
In their recent blog posting “Crossing the Software Education Chasm” for the Communications of the ACM Armando Fox and David Patterson from UC Berkeley address the tradeoff between university education of software engineers and actual expectations of employers. They suggest that a solution to reduce this gap consists of teaching students agile development of SaaS apps using tools like rails.
Phusion has released a preview release of their upcoming 3.2 version of Phusion Passenger. Version 3.2 comes with a re-written ApplicationPool, I/O handling is now event-driven and the Python support became a first-class citizen.
GitHub was recently compromised by a vulnerability in Ruby on Rails know as mass assignment. This vulnerability is thought to not only affect a large number of Ruby-based websites, but also those using ASP.NET MVC and other ORM-backed web frameworks.
Phusion announced that their Ruby 1.8.7 based Enterprise Edition (REE) is nearing its end-of-life. A Ruby 1.9 based version is not planned, instead the team focuses on Phusion Passenger, their solution for running Ruby on Apache and Nginx.
Travis CI, a cloud-based continuous integration (CI) offering for open source projects on Github, has announced support for Java builds, as well as Scala and Groovy additions. After gaining traction among the Ruby open source community the project is now looking into the possibility of expansion to a hosted CI service (nicknamed Travis Pro).
The Ruby on Rails team announced the first release candidate of Rails 3.2. New features include a faster development mode, an explain feature for database queries and several smaller features. After 3.2, the next major release of Rails will be 4.0 and drop support for Ruby 1.8.7
Exactly one year after the last major released, the Ruby on Rails team released Rails 3.1. The highlights of this release are support for HTTP Streaming, more intelligent migrations and the new assets pipeline that makes it easier to use CoffeeScript and Sass.
Play!, a Java Web Framework is now available on Heroku as a public beta. Play! is built on Netty and is well suited for handling asynchronous I/Os. It is based on a "share-nothing" stateless programming model.