Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ruby 3.4.0

ruby-lang.org

Post reply on HN
Print view View original

201–210 of 282 posts

Re: Ruby 3.4.0

#201

Post by dismalaf »

neonsunset wrote: post #111
zarzavat wrote: post #31

Earlier quoted context omitted.

Google hired all the best JIT engineers and set them to work on v8. If you want better performance you'd have to choose an AOT compiled language.

OpenJDK HotSpot and .NET RyuJIT both produce much faster code :) And the latter lets you operate on the same level of abstraction as Rust and C++ compilers do.

> OpenJDK HotSpot and .NET RyuJIT both produce much faster code :)

For dynamic languages? Stuff like Clojure, JRuby, Boo, are definitely not faster than V8 JavaScript...

Re: Ruby 3.4.0

#202

Post by dismalaf »

htunnicliff wrote: post #123
tuananh wrote: post #10

Shopify strategy aka the story of YJIT If I cannot refactor my services, I shall refactor Ruby instead.

For a stranger to the Ruby ecosystem, what are the benefits of YJIT?

Same as the benefits of JIT compilers for any dynamic language; makes a lot of things faster without changing your code, by turning hot paths into natively compiled code.

Re: Ruby 3.4.0

#203

Post by zahlman »

pjmlp wrote: post #39
tuananh wrote: post #10

Shopify 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…

>thankfully the whole AI focus has made JITs finally matter in CPython world as well.

Isn't most of the work in Python AI projects done in C or C++ extensions anyway?

Re: Ruby 3.4.0

#204

Post by blandflakes »

wiseowise wrote: post #49
briandear wrote: post #21

Earlier quoted context omitted.

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.

And of course the right way to do that is to take an extremely mediocre, rushed, incomplete language that is currently constrained to the browser, and make it run everywhere else, ironically having to reinvent many wheels and re-learn very old lessons the hard way along the way. Mission "reuse knowledge" is a hearty failure in node.js-land.

Re: Ruby 3.4.0

#205

Post by zem »

shortrounddev2 wrote: post #7

What does ruby do well that other languages don't? What is the niche it's trying to fill?

it's by far the best language I've found for writing a quick bit of code to explore a problem, or to do a one-off task. perhaps something about it just fits the way my brain works, but I find it incredibly easy to convert ideas to working ruby without having to think too hard about "okay, how do I actually express this in code".

Re: Ruby 3.4.0

#206

Post by malthaus »

fastball wrote: post #14
thdhhghgbhy wrote: post #12

Why did NodeJS take off on the backend while Rails was still popular? I'll never understand it.

Using the same language to write your frontend and backend is desirable for many people / teams.

but why does that language have to be one as braindead as javascript. path-dependency is the root of all evil.

Re: Ruby 3.4.0

#207

Post by riffraff »

ksec wrote: post #43
pjmlp wrote: post #35

I 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.

There's ongoing work to allow pluggable GCs, and specifically to allow using MMTk which would be IBM's Jikes GC

https://bugs.ruby-lang.org/issues/20470

https://www.mmtk.io/

Re: Ruby 3.4.0

#208

Post by never_inline »

wiseowise wrote: post #49
briandear wrote: post #21

Earlier quoted context omitted.

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.

> knowledge
Post reply on HN