What Would It Take for Roda to Win?— The creator of the Bridgetown site generator (which itself uses Roda at its heart) explains why he’s such a huge fan of the popular routing-oriented webapp library and how it bridges the gap between small and larger Ruby webapps better than, say, Sinatra. Jared White |
'I Built a Ruby Parser'— A story of a side project that led to Natalie, an early-stage alternative Ruby implementation with ahead-of-time compilation, and the up-and-down journey of getting to something that works. (Natalie can already work with a reasonable subset of Ruby, as seen in an example like this.) Tim Morgan |
![]() AppSignal Logbook: Team Discussion and Full Incident History— With Logbook you get the full incident history. Read and leave team comments, see which notifications were sent at what time, and see team activity for changes in incident states. It's easier than ever to see what the current state of an incident is. AppSignal sponsor |
Why GitLab is Sticking with Rails— The CEO of the popular git forge/devops platform reflects on why GitLab started with Rails (despite its founder coming from a PHP background) and why maintaining a ‘modular monolith’ continues to make sense for them. Sid Sijbrandij |
Senior Full Stack Engineer (Remote)— Help us in our transition from a collection of SPAs to a Rails+Hotwire application to rethink how modern real-time web-apps work.
Poll Everywhere |
Find Ruby Jobs Through Hired— Create a profile on Hired to connect with hiring managers at growing startups and Fortune 500 companies. It's free for job-seekers.
Hired |
|
Adding Feature Flags to a Rails App with Flipper— Flipper makes it reasonably easy to turn features on or off for specific users or groups of users, enabling a more granular way of testing new features on your app without throwing everyone in at the deep end. Hans-Jörg Schnedlitz (AppSignal) |
Anonymous Block Forwarding
Many of us have likely read or written Ruby code that takes a block argument and delegates it straight to another method. For example: def some_method(&block)
other_method(&block)
end
We name a block argument &block (or something similar) just to forward that &block argument to another method. Last year's Ruby 3.1 release introduced anonymous block forwarding when the argument is being passed to another method. This means that as of Ruby 3.1, you no longed need to name the block parameter and can instead use & . Our example above becomes: def some_method(&)
other_method(&)
end
If you're interested in adopting (or avoiding!) this style into your codebase, there's already a RuboCop cop for it! |
|
|