πŸš‚ This week in Rails πŸš‚: Learn How These 37 Rails Contributors Improved The Entire Framework In Just One Week

Posted by chancancode, August 21, 2015 @ 11:18 pm in News

Good News Everyone, This Week In Rails has been acquired by BuzzFeed!

Just kidding. This is Godfrey here. It’s been a while since I get to write one of these myself and I’m very happy to be back. Without further ado, let’s dive right into it!

❀️ Code of Conduct

The Rails team is committed to fostering a welcoming community for everyone. With the help of our community, we have added an official Code of Conduct for the project this week.

😱 37 Programmers Contributed To Rails And You Won’t Believe What Happened Next

Well, their pull requests were merged and they are immortalized on the Rails Contributors website. And oh, everyone please send a warm welcome to the 10 first-time contributors this week!

πŸ“¦ Releases πŸ“¦

πŸ“’ Sprockets Has Hit Version 3.3.3, What Does That Really Mean For The Rest Of Us?

According to @schneems who is responsible for the release, this is supposed to fix an issue for those of you β€œwho share a cache in different directories between deploys”, which includes Heroku deployments.

πŸ’Ž New Stuff πŸ’Ž

πŸ’Ύ MySQL Finally Gets A Native JSON Data Type – But Is It Too Late To Save California?

MySQL has recently added a native JSON data type (perhaps inspired by its more popular cousin, PostgreSQL). Thanks to this patch, you will be ready to take advantage of that feature in Rails 5.

πŸ‘Œ Fixed πŸ‘Œ

πŸŽ‚ The One Weird Trick That Lets You Write To Files Atomically

Concurrency is hard, but Rails might have finally cracked the nut. You might not know that Active Support offers a way to write to a file atomically with File.atomic_write.

Even if you have heard about it, you probably didn’t realize there is a subtle race condition in its implementation. Anyway, with this patch landing on master, those bugs will soon be behind us and we can all just sit back and enjoy the convenience it provides.

πŸ‘ Improved πŸ‘

🚨 Nobody Likes To Do Repeated Work – Here Is A Cache They Won’t Tell You About

It turns out that things do not run twice as fast when you double-cache them. Who would have thought? (I wish we all wrote great commit messages like this by the way!)

βœ‚οΈ Testing Is Important, But Has Rails Gone Too Far?

Along those same lines, it turns out that testing the same thing twice doesn’t provide much value either.

πŸ™ˆ Wrapping Up πŸ™ˆ

That’s all for This week in Rails. As always, there are many more changes than we have room to cover here, but feel free to check them out yourself!

Have you been thinking about writing for us, but you’re scared of putting yourself out there? Don’t worry, you can help our editors improve their writing with thoughtful critique and general grammar policing.

You up for that? Tell Godfrey today.