Rails 4.2.0 beta1: Active Job, Deliver Later, Adequate Record, Web Console
We’re putting the final touches on the first major new release of Rails in its second decade of life. While most software would be in a retirement home after a decade of operation, Rails has never been more fit, and this release is packed with goodies that’ll make your work even easier, your apps even faster, and the whole experience even better.
Active Job, ActionMailer #deliver_later
The headline feature for Rails 4.2 is the brand new Active Job framework, and its integrations. Active Job is an adapter layer on top of queuing systems like Resque, Delayed Job, Sidekiq, and more. You can write your jobs to Active Job, and they’ll run on all these queues with no changes.
With an always-configured queue in place (though the default is just an inline runner), we can build on top of that where it makes sense. And the first place it makes sense is to send Action Mailer emails asynchronously. So we’re introducing the #deliver_later method, which will do just that: Add your email to be sent as a job to a queue, so you don’t bog down the controller or model. Voila!
The cherry on top is our new GlobalID library. It makes it easy to pass Active Record objects to jobs by serializing them in a generic form. This means you no longer have to manually pack and unpack your Active Records by passing ids. Just give the job the straight AR object, and it’ll serialize it using GlobalID, and deserialize it at run time. So much easier!
Special thanks go out to Cristian Bica and Abdelkader Boudih for their outstanding work bringing this trinity of improvements to Rails!
Adequate Record
Aaron Patterson is always hunting for performance bounties in Rails, and with an improvement project called Adequate Record for Active Record, he’s come up good. A lot of common queries are now no less than twice as fast in Rails 4.2! This is a great step forward for performance. While computers are constantly getting cheaper and performance is improving, nobody ever said “hey, get that free speed out of my framework”. So there you go: Some free speed, buddy!
Web Console
Out of the wonderful Google Summer of Code for Rails campaign comes Web Console. It’s an IRB console available in the browser. In development mode, you can go to /console and do your work right there.
Now that’s neat, but what’s insanely useful is that this console is automatically available on all exception pages! So when something is bust, you’ll now instantly be able to inspect the state of affairs. It even allows you to jump between the different points in the backtrace, and you’ll be able to inspect things right at that point.
It’s a wonderful improvement to the debugging workflow. Thanks to Genadi Samokovarov and Ryan Dao for their work on this project.
Everything else
Some quick highlights from the rest of all the wonder that is Rails 4.2:
- Template digests are now automatically included when calculating etags for caching. So caches are bust when the template changes.
respond_withhas moved out and into its own proper home with the responders gem.- Support for real foreign keys!
add_foreign_key/remove_foreign_keyare now available in migrations. - A ton of bug fixes and minor improvements to Active Record.
- Added
config.x.whatever.you_want = truefor custom configuration of your app inconfig/environments/*,config/application.rb, and initializers. - Added
Rails::Application.config_for(:some_yaml)to load YAML configurations store inconfig/easily.
We’re working on a set of preliminary release notes too.
Maintenance consequences and Rails 5.0!
As per our maintenance policy, the release of Rails 4.2 will mean that bug fixes will only apply to 4-2-stable, regular security issues to 4.2.x, 4.1.x, and severe security issues to 4.2.x, 4.1.x, and 3.2.x. In addition to these already stated commitments, the honorable Rafael França has agreed to also apply bug fixes to 4-1-stable. So everyone still on 4.1 and unable to move quickly can thank Rafael!
Rails 4.2 will also mark the last big release in the 4.x series. After release, we’re going to work towards the big Rails 5.0! This means rails/master will have that target as soon as the release candidates for 4.2 start, and 4-2-stable is created.
Rails 5.0 is in most likelihood going to target Ruby 2.2. There’s a bunch of optimizations coming in Ruby 2.2 that are going to be very nice, but most importantly for Rails, symbols are going to be garbage collected. This means we can shed a lot of weight related to juggling strings when we accept input from the outside world. It also means that we can convert fully to keyword arguments and all the other good stuff from the latest Ruby.
The release target for Rails 5.0 is currently spring/summer of 2015. So there’s a while yet, but we’re putting this out there for people to know, so gem maintainers and other Ruby implementations can know where we’re going.
Please help us make Rails 4.2 solid!
We rely on the feedback from everyone in the community to flush out bugs and upgrade issues ahead of a big release like this. So please give Rails 4.2 a try on your app, and if you’re starting a new app today, you should probably use the beta1 for that, if you’re just the least bit savvy with Rails.
Issues can be recorded on the Github issues tracker.
Already, 476 people have contributed to this new release of Rails. Please do become one of them!