https://railsatscale.com/2025-05-21-fast-allocations-in-ruby-3-5/ #Ruby3.5 #SpeedDemon #ObjectAllocation #PerformanceBoost #CodeOptimization #HackerNews #ngated
π€ Upgrading to Ruby 3.0 and using the i18n gem?
Be careful with the gotcha of the "frozen?" method.
The gem behaves differently in Ruby 2.7 vs Ruby 3.0. π οΈ You'll want to stay
ahead of the curve before upgrading to Ruby 3. Rishi does a full analysis:
https://www.fastruby.io/blog/ruby-3-i18n-gem-and-beyond.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=gemgotchas&utm_content=Textonly
[https://www.fastruby.io/blog/ruby-3-i18n-gem-and-beyond.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=gemgotchas&utm_content=Textonly]
#rubyonrails#rails #ruby3 #rubygems #i18n
Explore the intricacies of upgrading from Ruby 2.7 to 3.0, uncovering i18n gem pitfalls involving clone and freeze methods. Valuable insights for tech teams navigating this transition.
π‘ Cloning objects in Ruby 3.0 has its quirks, especially with the #i18n gem.
@jainrishi15 did some digging and here's what he found:
https://www.fastruby.io/blog/ruby-3-i18n-gem-and-beyond.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=gemgotchas&utm_content=Textonly&utm_id=
#rubyonrails #Ruby3 #rubygems #RubyLang #Ruby27
Explore the intricacies of upgrading from Ruby 2.7 to 3.0, uncovering i18n gem pitfalls involving clone and freeze methods. Valuable insights for tech teams navigating this transition.
"Since we were interested in deprecation warnings related to Ruby 3.0 only, we filtered all the deprecations by looking for only certain keywords that are of interest to us. We configured all such keywords in an environment variable called ALLOWED_EXCEPTION_KEYWORDS [...]"
Check out this insightful article to learn more about the #Ruby3 upgrade process: https://www.fastruby.io/blog/my-journey-upgrading-to-ruby-3-0.html#:~:text=Since%20we%20were%20interested%20in%20deprecation%20warnings%20related%20to%20Ruby%203.0%20only%2C%20we%20filtered%20all%20the%20deprecations%20by%20looking%20for%20only%20certain%20keywords%20that%20are%20of%20interest%20to%20us.%20We%20configured%20all%20such%20keywords%20in%20an%20environment%20variable%20called%20ALLOWED_EXCEPTION_KEYWORDS
I share the approach I took to upgrade Ruby from 2.7 to 3.0 when the test coverage was low. Some of the decisions were taken to fit the needs of the project and may not apply all the time.
π‘ Cloning objects in Ruby 3.0 has its quirks, especially with the #i18n gem.
@jainrishi15 did some digging and here's what he found:
https://www.fastruby.io/blog/ruby-3-i18n-gem-and-beyond.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=gemgotchas&utm_content=Textonly&utm_id=
#rubyonrails #Ruby3 #rubygems #RubyLang #Ruby27
Explore the intricacies of upgrading from Ruby 2.7 to 3.0, uncovering i18n gem pitfalls involving clone and freeze methods. Valuable insights for tech teams navigating this transition.
We are excited to share @jainrishi15's journey upgrading to Ruby 3! π
"The first thing we did was handle all the Ruby 3.0 related deprecations."
Check out this insightful article to learn more about the process: https://www.fastruby.io/blog/my-journey-upgrading-to-ruby-3-0.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=upgrading-ruby-3&utm_content=Photo&utm_id=
I share the approach I took to upgrade Ruby from 2.7 to 3.0 when the test coverage was low. Some of the decisions were taken to fit the needs of the project and may not apply all the time.
We are excited to share @jainrishi15's journey upgrading to Ruby 3! π
"The first thing we did was handle all the Ruby 3.0 related deprecations."
Check out this insightful article to learn more about the process: https://www.fastruby.io/blog/my-journey-upgrading-to-ruby-3-0.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=upgrading-ruby-3&utm_content=Photo&utm_id=
I share the approach I took to upgrade Ruby from 2.7 to 3.0 when the test coverage was low. Some of the decisions were taken to fit the needs of the project and may not apply all the time.
We are excited to share @jainrishi15's journey upgrading to Ruby 3! π
From improved performance to new syntax, Ruby 3.0 offers some fantastic features!
Check out this insightful article to learn more about the process: https://www.fastruby.io/blog/my-journey-upgrading-to-ruby-3-0.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=upgrading-ruby-3&utm_content=Photo&utm_id=
I share the approach I took to upgrade Ruby from 2.7 to 3.0 when the test coverage was low. Some of the decisions were taken to fit the needs of the project and may not apply all the time.
We are excited to share @jainrishi15's journey upgrading to Ruby 3! π
From improved performance to new syntax, Ruby 3.0 offers some fantastic features!
Check out this insightful article to learn more about the process: https://www.fastruby.io/blog/my-journey-upgrading-to-ruby-3-0.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=upgrading-ruby-3&utm_content=Photo&utm_id=
I share the approach I took to upgrade Ruby from 2.7 to 3.0 when the test coverage was low. Some of the decisions were taken to fit the needs of the project and may not apply all the time.
π Noticed a change in the "frozen?" method with the #i18n gem?
Rishi uncovers a "gotcha" that's tricky to understand. If you're upgrading to Ruby 3, get ahead of the curve. π΅οΈββοΈ
Explore the intricacies of upgrading from Ruby 2.7 to 3.0, uncovering i18n gem pitfalls involving clone and freeze methods. Valuable insights for tech teams navigating this transition.