Earlier quoted context omitted.
Do you have any evidence that it's been used less and less?
https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0...
this is evidence of google searches. nothing more.
Ruby 3.4.0
41–50 of 282 posts
Re: Ruby 3.4.0
#42Shopify strategy aka the story of YJIT If I cannot refactor my services, I shall refactor Ruby instead.
That has been the story of every dynamic language since forever, thankfully the whole AI focus has made JITs finally matter in CPython world as well. Personally I have learnt this lesson back in 2000's, in the age of AOLServer, Vignette, and our own Safelayer product. All based on Apache, IIS and Tcl. We were early adopters of .NET, when it was only available to MSFT Partners and never again, using scripting language…
[dead]
Re: Ruby 3.4.0
#43I am liking all the performance improvement goodies on JIT and GC level.
1. Wondering 3.4 JIT performance vs 3.3 JIT on production rails.
2. Also wondering what upside could Ruby / Rails gain on a hypothetical Java Generational ZGC like GC? Or if current GC is even a bottleneck anywhere in most Rails applications.
Re: Ruby 3.4.0
#44‘it’ is a welcome addition!
Truly is, much nicer than that lonely `_1`
Re: Ruby 3.4.0
#45Earlier quoted context omitted.
It's the language with the highest ratio of (useful work / LOC), so it's the least verbose language. This makes it very suitable to write and understand complex scripts, because the reduced boilerplate means less cognitive overhead for the programmer. As a result, experienced programmers can be extremely productive with it. The well-known Rails framework uses this to great effect, however, some people argue that the…
Experienced teams love magic?
It depends which kind of magic. Everybody love some magic to be in its life, as long as it doesn't reveal to be a curse unintentionally coming out from a good willing wish.
Also you don't want all and everything being the results of spells you don't have a clue how they are cast.
Re: Ruby 3.4.0
#46Earlier quoted context omitted.
https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0...
this is evidence of google searches. nothing more.
There's also the TIOBE index: https://www.tiobe.com/tiobe-index/ruby/
It conveys similar trend to Google Search chart
Re: Ruby 3.4.0
#47What does ruby do well that other languages don't? What is the niche it's trying to fill?
Ruby has the nicest object-oriented design (everything is an object) outside of smalltalk (IMHO). In contrast to the mess that is Python. For instance, in Ruby it is natural that each or map are methods of Array or Hash rather than global functions which receive an Array or Hash argument. This goes as far as having the not operator '!' as a method on booleans: false.! == true Once you have understood it, it is a very…
It's very powerful though which is a bit terrifying. You can literally monkey patch Object at runtime and add methods to every single instantiated object! (I believe this is how rspec works..)
Awesome, but with great power come great responsibility ;)
Re: Ruby 3.4.0
#48Earlier quoted context omitted.
this is evidence of google searches. nothing more.
There's also the TIOBE index: https://www.tiobe.com/tiobe-index/ruby/ It conveys similar trend to Google Search chart
Because it uses same metrics.
If you want to see real usage statistics you need to consult GitHub, JetBrains, RedMonk ratings.
Re: Ruby 3.4.0
#49Why did NodeJS take off on the backend while Rails was still popular? I'll never understand it.
Because of the JavaScript Everywhere crowd. When you have a hammer, everything looks like a problem for JavaScript.
God forbid we reuse knowledge instead of drudging lives through never ending learning of same concepts with different syntax’s and 10x costs for supporting every special native snowflake toolchain.
Re: Ruby 3.4.0
#50I am liking all the performance improvement goodies on JIT and GC level.
1. Wondering 3.4 JIT performance vs 3.3 JIT on production rails. 2. Also wondering what upside could Ruby / Rails gain on a hypothetical Java Generational ZGC like GC? Or if current GC is even a bottleneck anywhere in most Rails applications.
Most likely not yet there, but for applications implemented in Ruby it is certainly an improvement for overall usability experience.