Short Ruby News - edition #20

Briefly about everything in Ruby world

Nov 28, 2022

This edition was created with the help of @adrianthedev/@adrian@ruby.social from Avo for Ruby on Rails (a friendly full-featured Rails admin panel) and @jcsrb.

You can jump directly to one of the following sections if you like:

👐 Our Community

👉 All about Code and Ruby

🧰 Gems, Libraries, and Updates

🤝 Related (but not Ruby-specific)

More content: 🎥 🎧 🗞 (articles, podcasts, videos and newsletters)

👐 Our Community

👐 Hanami 2.0 was released. Read the release notes here.

👐 Ruby versions 3.1.3, 3.0.5 and 2.7.7 are released:

Related to this, Postmodern announced that ruby-versions now support all these three versions.

👐 Jean Boussier about Ruby/Rails:

🤝 Cezar Halmagean is offering all Short Ruby subscribers/readers a 40% discount for his course Learn Hotwire . Use coupon code SHORTRUBY (valid until Tuesday) at the checkout :

Learn Hotwire

👉 All about Code and Ruby

👉 Greg Navis shared a thread about constant autoloading. Read the whole thread about how constant autoloading works:

👉 Chris Oliver asked about deals for Ruby & Rails. Some of them were available for Friday, but I think you should check them out as most of them are still available:

Here is a list of links (that today - Sunday seems still to be valid) from the replies:

Go Rails and Jumpstart Pro
Avo - CMS and CRM builder on Ruby on Rails (use code RUBY20BF)
Book time with Ian Moss
Spektr - vulnerability Scanning for Ruby on rails app - all plans free
Rebuilding Rails book by Noah Gibbs
Deployment from Scratch by Josef Strzibny
Advanced CableReady by Julian Rubisch
StimulusReflex Patterns Premium + Advanced CableReady Bundle by Julian Rubisch
Pragmatic Programmer books are 40% off (code turkeysale2022) - that includes Programming Ruby 3.2 and Modern Front-End Development for Rails by Noel Rappin
Product Focused Ruby by Kasper Timm Hansen

👉 Mehdi Farsi shared a short code explaining the difference between ! and not:

If you want to understand more unary operators (the method ending with @) here is an example:

👉 James shared a new project he is working on rubymyths.dev and here is the reason why:

If you want to know who was the one that inspired this and what they shared, read here

👉 Joel Drapper asked about why senior/principal engineers are asked basic Rails take-home coding challenges:

The thread also has some ideas about how a conversation about hiring senior developers could be.

👉 Kelly Sommers shared a joke that Mastodon seems slow, and it implied this is because of Ruby:

Sam Saffron replied:

Nate Berkopec pointed out that maybe Ruby is not the issue here:

And also added that the X-runtime header is showing 92 milliseconds runtime:

I am adding something here: Kelly said they shared this as a joke, but this is a joke that is not so obvious and implies that Ruby is slow. Thus please take time to read the thread, as this kind of critique, sometimes thrown in a lightweight way, will influence decisions. It will help you be prepared to have this conversation.

👉 Jason Swett shared they are starting Code With Jason Salon. Register here if you want to participate:

👉 Joel Drapper shared a code preview showing conditional tokens support in the next version of Phlex:

👉 Greg Navis shared a thread about using then to sequence operations:

👉 Kirill Shevchenko shared a code sample about using the ActiveSupport built-in module for configuration:

👉 Greg Navis shared a thread about currying in Ruby. There are a lot of code samples there so here are two

👉 Peter Solnica shared a code sample showing how providers work in Hanami:

👉 Greg Molnar asked about Rspec or Minitest:

Here is a summary of reasons for choosing Minitest:

It is simple
It is fully supported by Rails.
It is easier to reason with
It is easy to onboard new developers as there is no new DSL to learn

And here is a summary of reasons for choosing RSpec:

Because a lot of people are using it
needs less code to achieve the same test case as with Minitest
Rspec seems less boring than Minitest

Worth considering listening to this YAGNI episode: RSpec w/ Justin Searls

👉 Joel Drapper started a discussion about method overload in Ruby (please be advised this does not work):

And this got a lot of gems proposing various ways to achieve this:

Jamie Gaskins shared their gem method_pattern:

Source: https://github.com/jgaskins/method_pattern

Brandon Weaver shared their gem taking:

Source: https://github.com/baweaver/taking#usage

Paweł Świątkowski shared their own gem noaidi:

Source: https://github.com/katafrakt/noaidi

👉 Lucian Ghinda asked about examples of using the endless method:

Here are some responses:

"Using it when the method is exactly one line with no logic (not even ||=)“ (@davetron500@ruby.social)
“saw someone used it to replace the rails “scope” class method” (@schneems@ruby.social)
“I often use them for methods that are a single statement (not line, statement)” (@joeldrapper@ruby.social)
“I use it mostly as a signal that the method is basically a computed attribute -- it's a single statement, and usually takes no arguments.” (@noelrap@ruby.social)
“I use it with one-liners, mostly like I'm using one-liners in Elixir. Just return data, no mutations or memorization” (@katafrakt@ruby.social)
“Only use Ruby 3.0’s endless method definitions with a single line body. Ideally, such method definitions should be both simple (a single expression) and free of side effects.” (rubystyle.guide)