Rails 3 Release Candidate Announced!
Posted at 8:23 | 20 Jul. 2022
Tweet this story | Share on Facebook | Email to a Friend
Rails 3 Release Candidate - A closer look

this week 12 years ago the release candidate for Rails 3 was announced. Wow - this was a monumental release and I can't help but thinking how far we've come since then. Strong parameters, ActiveStorage, ActionCable, Rails API mode, webpacker and back, and even Hotwire! But there's no doubting this was a big game-changing release for the Rails community. Click through and read through the exciting announcement here
Ruby 2 Keyword Arguments

On this week eight years ago Thoughtbot put out a fantastic blog talking about keyword arguments that were introduced in Ruby 2.0. Sometimes I take certain things for granted in our ecosystem, keyword arguments definitely is one of those things. Enjoy this great work from Ian C. Anderson!
article
Block and Lambda

I'm sorry. I really find it hard to go an issue without sharing some of the great discussions from Why The Lucky Stiff from back in the day. This week is now different. Today SEVENTEEEN years ago _why hosted a great summary and discussion about some of the debates around a new shared block and lambda syntax. If you want to geek out about blocks and lambdas, this is just what the doctor ordered.
opinion
Backgrounded - a background process wrapper in Ruby

This week thirteen years ago saw the initial fanfare for "backgrounded", which was an early background job framework. It provided a simple, elegant approach to invoking background jobs in ruby. Or as the author said in 2009: " I'm going to come right out and say it... Every ruby background job solution sucks. I've used a number of the popular libraries on various projects over the past year, and have yet to find one that "feels right". They took an incredibly complex problem and made and even more complex solution. It really shouldn't be this hard. All I want to do is take a unit of work from my model and kick it off into "magical background job land". I don't want to create separate "Worker" or "Job" classes which only exist to call back into my model object. If your background jobs are doing more work than that, you're doing something wrong! "
Archive
- Rails 3 Release Candidate Announced! | July 2022
- I'd Want to Work on Ruby When I Grow O-o-old | April 2022
- When RubyKaigi tickets sold out in 60 minutes | April 2022
- ActiveRecord is Released! | April 2022
- Ruby tools roundup | October 2021
- The second oldest Rails podcast? | October 2021
- Running every version of Ruby ever released with All-Ruby | September 2021
- Ruby Multithreading | September 2021
- Indexing database columns in 2009 | September 2021
- Matz talks mRuby at Barcelona Ruby Conf 2014 | September 2020
- Github: Scaling on Ruby with a nomadic tech team | July 2020
- 22 Ruby and Rails Jobs for August 2011 (With Even Some Junior Ones) | July 2020
- The schedule for Madison Ruby 2011 | July 2020
- What to expect in Ruby 1.9 (2008) | July 2020
- Matz speaks at OSCON | July 2020
- How to profile your Rails application in 2007 | July 2020
- RubyFringe: the three-day, $650 Ruby party of 2008 | July 2020
- A Starry Afternoon, a Sinking Symphony, and the Polo Champ Who Gave It All Up for No Reason Whatsoever | July 2020
- Using AWS with Ruby in 2007 | June 2020
- RubyConf 2005 Agenda Release | June 2020
- _why interviews DHH [PastRubies #9] | December 2019
- The Ruby on Rails Whitepaper - Past Rubies #7 | December 2019
- Speeding Up Rails with Aaron Patterson - Past Rubies #6 | July 2019
- Building a Ruby Gem with Steve Klabnik - Past Rubies #5 | July 2019
- Rails 1.0 turns 14! PastRubies #8 | December 2019