😒 Oh, the drama! #Ruby 3.4 is tiptoeing towards frozen string literals, and #Rails developers are about to be "warned" to... do absolutely nothing different. 🎭 Spoiler alert: your app still works, just like it did yesterday. 🙄
https://www.prateekcodes.dev/ruby-34-frozen-string-literals-rails-upgrade-guide/ #Drama #FrozenStringLiterals #AppDevelopment #HackerNews #ngated

Ruby 3.4 Frozen String Literals: What Rails Developers Need to Know

https://www.prateekcodes.dev/ruby-34-frozen-string-literals-rails-upgrade-guide/

#HackerNews #Ruby34 #FrozenStringLiterals #RailsDevelopers #UpgradeGuide #RubyOnRails #ProgrammingTips

#ProTip Never waste an opportunity to rant against language/ecosystem misfeatures! I never tire of complaining about the overuse of #FrozenStringLiterals in #RubyLang, or the over-reliance on community style guides as a stand-in for #codequality instead of using #TDD, intentional semantics, or good variables/comments.

If you don't trust other #Rubyists to understand `[].any? ? complain : shut_up` without an extra 4 lines of if/else bloat in your method, the real problem isn't the ternary!

Okay, so yesterday I made some statements about #RubyLang #FrozenStringLiterals . I'm still trying to come up with some code that proves a point, but think it's more of a #StackOverflow question. I tried creating memory bloat with frozen strings, which most people agree are represented with a Symbol (see :intern) but the :object_id may or may not be the same depending on various things.

I hate making material errors, so please just take my frozen strings rants as frustration with the docs.