Because they care more about getting things done than whether clout-chasers think they're "cool".

you'd like go then.

I get things done just fine with Go. And all the code is very clear. With ruby it is not, and a lot of ruby programmers may have a feel about how things work, while they are not really. They just enjoy the syntax. The book "The Ruby Programming Language" which written by the creator or ruby (I forgot his name) is full of "unfortunately", unfortunately this works this way now, unfortunately that works that way now.

And people definitly chose ruby because it was cool. So what you said should be applied to Ruby, not Go.

Since they left ruby (2.0) raw rails performance improved by 75% (3.0)

https://www.fastruby.io/blog/assets/images/RRBPerfHistory_72...

Then in 3.2, ruby released YJIT which improved median rails response time by about 100%

https://raw.githubusercontent.com/easydatawarehousing/ruby_m...

It's kind of a golden era for rubyists that stuck it out. Beautiful maintainable code that hits C performance for many tasks.

"... hits C performance for many tasks"

Really?

particular improvements that come closer to C are related to string operations and regex

https://tomaszs2.medium.com/ruby-3-2-0-is-from-another-dimen...

Wow

Didn't know that, thanks for the update. Actually, now I want to give it a try, remembering my old romantic days.