Ruby 3.4 frozen string literals: What Rails developers need to know
1–10 of 131 posts
Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#2Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#3Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#4Would Ruby be as successful if they had all those complicated features right from the start ?
Or do all languages start from a nice simple clean slate tabula rasa to get developers hooked, until the language is enough famous to get well developed and starts to be similar to all others big programming languages ?
Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#5Is it the future path of any successful JIT / dynamic typed / scripting language to realize they needed all optimizations from compiled / statically typed / lower level languages ? Would Ruby be as successful if they had all those complicated features right from the start ? Or do all languages start from a nice simple clean slate tabula rasa to get developers hooked, until the language is enough famous to get well de…
Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#6Is it the future path of any successful JIT / dynamic typed / scripting language to realize they needed all optimizations from compiled / statically typed / lower level languages ? Would Ruby be as successful if they had all those complicated features right from the start ? Or do all languages start from a nice simple clean slate tabula rasa to get developers hooked, until the language is enough famous to get well de…
Mutable strings are totally possible (and not even especially hard) in compiled, statically typed, and lower-level languages. They're just not especially performant, and are sometimes a footgun.
> all those complicated features right from the start
Arguably, mutable strings are the more complicated feature. Removing them by default simplifies the language, or at least forces you to go out of your way to find the complexity.
Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#7An obviously good change, actually massive performance improvements not hard to implement but its still gonna be such a headache and dependency hell
Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#8TIL that Ruby has mutable strings, and (until the announced change) even had them mutable by default (and the change only affects literal strings; non-literal strings are still mutable). Python has always only ever had immutable strings.
Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#9We learned nothing from Python 2->3 An obviously good change, actually massive performance improvements not hard to implement but its still gonna be such a headache and dependency hell
Re: Ruby 3.4 frozen string literals: What Rails developers need to know
#10TIL that Ruby has mutable strings, and (until the announced change) even had them mutable by default (and the change only affects literal strings; non-literal strings are still mutable). Python has always only ever had immutable strings.