This week in Rails
Welcome to This week in Rails, your weekly inside scoop of interesting commits, pull requests and more from Rails. Without further to do, let's dive right into the highlights of the week!
A critical issue that appears to affect many users has been reported this week. The core team has acknowledged the report and has plans to address this down the road. Stay tuned.
Many of you have responded to the call for help to improve the 4.2 documentations over the last week. Thank you so much, please keep it coming! <3
So far, 34 contributors have helped improve Rails this week, 6 of them being first-time contributors. Welcome to the team!!! <3 <3 <3
Yet another way to try nil things in Rails 4.2.
While methods like try provides great convenience, they do come at a cost (as Aaron would say, allocations aren't free!) that adds up in when used in hot paths.
While the cost is usually outweighted by the convenience in application code, it's always good to measure all the things in order to make informed tradeoff decisions (learn how)!
With this fix, Rails should no longer uglify your queries on PostgreSQL. Assuming we don't find other regressions, you should expect another RC dropping soon™.
In case you missed it, this pull request pointed out that it is considered best practice to pass log messages using the block form when there are interpolated code in your log messages.
And that's it for this issue of This week in Rails. As always, there are a lot more changes on Rails than what I can cover in this newsletter, so I encourage you to check them out yourself!
If you have any feedback for me, please feel free to email me or let me know on twitter! Thank you for reading! <3 <3 <3
P.S. Feel free to share this newsletter with your Rails friends!