I am not sure how this contributes to the unfounded idea that ruby is dead—Shopify, Stripe, and GitHub amongst many others would like a word.
RubyMine isn’t the editor of choice for many of my fellow rubyists, but it is for me—IntelliJ’s LSP alone is a godsend when you’re diving deep into debugging weird gems. I have tried ruby-lsp from Shopify and it gets 95% there but that last 5% is what makes me hyper-productive.
Most of the community is on VS Code. We did have a weird, loud Danish guy using TextMate until recently, but I guess he switched to neovim.
Having said, RubyMine was very popular when ruby was on HN as much as AI is today. It hasn’t kept up, just like Sublime has been largely replaced by VS Code.
> Shopify, Stripe, and GitHub
Yeah I mean Facebook, Wordpress, Wikipedia... but are you going to start a new project in PHP today? I bet all of them wish they weren't using Ruby. (Well probably not because they'll attract devs that love Ruby, but you get the point...)
Anyway in terms of concrete numbers the best thing I've found is to look at Github PRs/projects/stars. This site is really cool: https://madnight.github.io/githut/
Ruby was quite popular at the start of the chart in 2014 when it was more popular than Java! But gradually waned until about 2020 where it seems to have stabilised at "not very popular", just behind PHP.
Go and Typescript seem to have taken its place, which makes sense because they're both much better languages.
> I bet all of them wish they weren't using Ruby.
I've never heard any entrepreneur say they wish they didn't use Ruby... Nothing I've ever seen gets you from zero to a fully working CRUD website nearly as quickly.
The only people who say such things are the ones who didn't pick it.
> I bet all of them wish they weren't using Ruby.
I'd take that bet. At scale, (and those 3 are the definition of scale) you can mitigate some of the downsides of Ruby (i.e. speed), but you can't recreate the upsides (i.e. developer satisfaction, learning curve, flexibility) elsewhere.
> Go and Typescript seem to have taken its place, which makes sense because they're both much better languages.
Again: depends on the metrics you're considering. I would certainly consider Go much better than ruby on some metrics, but most definitely not all - and importantly, if I put all of it on a scale (and this is where bias comes in), I still give the edge to Ruby over both of those.
Heh, not the person you were replying to, but I do not find the list of upsides compelling. These products at scale are mature (minus everyone’s list of personal bugs and misfeatures). Who cares how easy it is to pick up the language or developer happiness? A stricter language with more hard guarantees makes it possible to make changes to a big code base without fear.
Fair! And yep, I too wish Ruby was stricter. I just happen to value it slightly less than some of the things I do get with the language.
> Who cares how easy it is to pick up the language or developer happiness?
Someone who's building a startup. Time to market and not succumbing to the desire to quit is #1 when you're building from the ground up.
You DGAF about making changes to a large codebase when you have no codebase...
Sure but at scale the downsides of Ruby become even more significant - performance is more of an issue at scale, as is the lack of static typing.
I don't think Typescript or Go have a worse developer experience or learning curve than Ruby. You can learn Go in a week. They both have better tooling and higher developer satisfaction (admired/desired) scores than Ruby according to Stackoverflow's survey.
That’s not a good indicator at all. Open source requirements are very different from business application.
I'm weird. I'm still using the RoR Plugins for NetBeans. It still works pretty great (including haml and coffee autocomplete and code highlighting) for maintaining some legacy apps if you don't intend to reinstall it from scratch (which is a nightmare).
>Shopify, Stripe, and GitHub
Outliers do not dictate the mean.