Ruby is starting at a knowledge/awareness deficit and long term it's going to be hard to keep a quality edge to make up for that.
On the other hand, the interest in it is simply declining, and consistently so (check out the Google trends post above).
> Ruby is finally improving it’s static analysis, async and threading weaknesses.
They're great things (not sure if with "static analysis" you refer to static typing), although threading will never be realistically adopted, giving the 25+ years long history of thread-unsafety (both in terms of library and culture).
I was thinking more like AST based tools, although static typing is very helpful.
I think we've discussed threading stuff before, I take your points but I'm still hopeful to see how things pan out in the next few years.
People have been saying Ruby on Rails will go no where since it launched. So far their 5 year predictions have always been wrong.
Personally, I think startups are exciting. I think Rails will still be a favourite with startups in 5 years time because it lets you build MVPs fast. It gives you sensible defaults for things that don’t matter that much but doesn’t enforce them.
The latest updates to to Ruby 3.1 and Rails 7 let you build even faster.
As you mention Ruby on Rails now has a compelling answer to writing frontend JavaScript in Hotwire and Stimulus.
It will soon have a compelling answer to mobile apps too.
Ruby is finally improving it’s static analysis, async and threading weaknesses.
I don’t mind if it’s boring, I’d still bet that Ruby on Rails will be even better for it’s niche in 5 years time.
It’s a safe bet when everything else in startup land is risky.