Unveiling the big leap in Ruby 3.3's IRB

Re:Unveiling the big leap in Ruby 3.3's IRB by bogota on Sunday December 24, 2023 @01:15AM (#38751560)

And also produces so much waste since almost no one writing python thinks at all about performance leading to some of the dumbest looking architectures i have seen to scale up to even a small amount of requests.

[ Parent | on HN ]

Re:Unveiling the big leap in Ruby 3.3's IRB by oblio on Sunday December 24, 2023 @06:15AM (#38752727)

And your counterargument to that is... Ruby?

[ Parent | on HN ]

Re:Unveiling the big leap in Ruby 3.3's IRB by Qem on Sunday December 24, 2023 @03:04PM (#38756339)

Nowadays Ruby has built-in JIT compilation, through YJIT.

[ Parent | on HN ]

Re:Unveiling the big leap in Ruby 3.3's IRB by oblio on Monday December 25, 2023 @07:23AM (#38762033)

Isn't that the thing where it outputs C and then compiles the C code and then runs that?

[ Parent | on HN ]

Re:Unveiling the big leap in Ruby 3.3's IRB by ric2b on Monday December 25, 2023 @10:48AM (#38763538)

Yes, but it caches the generated code, so if you run a function 1000 times you only pay the compilation cost once.

[ Parent | on HN ]