home.social

#ruby3 β€” Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ruby3, aggregated by home.social.

  1. πŸš€πŸ’¨ Ruby 3.5 just unleashed a speed demon on object allocations! But wait, you thought your app was slow because of the code? πŸ˜‚ No, it just needed more horsepower under the hood. Don't worry, there are graphs for those who need to look busy at work. πŸ“ˆπŸ’Ό
    railsatscale.com/2025-05-21-fa #Ruby3.5 #SpeedDemon #ObjectAllocation #PerformanceBoost #CodeOptimization #HackerNews #ngated

  2. πŸš€πŸ’¨ Ruby 3.5 just unleashed a speed demon on object allocations! But wait, you thought your app was slow because of the code? πŸ˜‚ No, it just needed more horsepower under the hood. Don't worry, there are graphs for those who need to look busy at work. πŸ“ˆπŸ’Ό
    railsatscale.com/2025-05-21-fa #Ruby3.5 #SpeedDemon #ObjectAllocation #PerformanceBoost #CodeOptimization #HackerNews #ngated

  3. πŸš€πŸ’¨ Ruby 3.5 just unleashed a speed demon on object allocations! But wait, you thought your app was slow because of the code? πŸ˜‚ No, it just needed more horsepower under the hood. Don't worry, there are graphs for those who need to look busy at work. πŸ“ˆπŸ’Ό
    railsatscale.com/2025-05-21-fa #Ruby3.5 #SpeedDemon #ObjectAllocation #PerformanceBoost #CodeOptimization #HackerNews #ngated

  4. πŸš€πŸ’¨ Ruby 3.5 just unleashed a speed demon on object allocations! But wait, you thought your app was slow because of the code? πŸ˜‚ No, it just needed more horsepower under the hood. Don't worry, there are graphs for those who need to look busy at work. πŸ“ˆπŸ’Ό
    railsatscale.com/2025-05-21-fa #Ruby3.5 #SpeedDemon #ObjectAllocation #PerformanceBoost #CodeOptimization #HackerNews #ngated

  5. 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: fastruby.io/blog/my-journey-up

    #Ruby3 #UpgradeRuby #TechDebt

  6. 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: fastruby.io/blog/my-journey-up

    #Ruby3 #UpgradeRuby #TechDebt

  7. πŸ€” 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: fastruby.io/blog/ruby-3-i18n-g

    #rubyonrails #rails #ruby3 #rubygems

  8. πŸ€” 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: fastruby.io/blog/ruby-3-i18n-g

    #rubyonrails #rails #ruby3 #rubygems

  9. πŸ€” 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: fastruby.io/blog/ruby-3-i18n-g

    #rubyonrails #rails #ruby3 #rubygems

  10. πŸ€” 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: fastruby.io/blog/ruby-3-i18n-g

    #rubyonrails #rails #ruby3 #rubygems

  11. πŸ€” 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: fastruby.io/blog/ruby-3-i18n-g

    #rubyonrails #rails #ruby3 #rubygems

  12. Is there any timeframe about when to expect pry-doc to support #Ruby3? #PryRepl βž™ github.com/pry/pry

  13. About the new feature in #Ruby 3: Am I the only one who reads #Rancor first and then Ractor? One of them is really cool (certainly on an 8 core machine), the other is not exactly beautiful. πŸ™‚ #Ruby3 #ActorModel