Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
The Waning of Ruby and Rails (berk.es)
9 points by berkes on March 8, 2022 | hide | past | favorite | 5 comments


Few small errors:

> Stripe (2011)

Stipe doesn't use Rails at all. They use Ruby only.

>Discord and Mastodon

I assume you mean Discourse, the forum. Discord, the Chat App, uses Elixir + Rust

>Running Rails and started after 2010

Gusto (2012), Instacart (2012), Coinbase (2012), FlexPort (2014),

Although I agree with the overall thesis of the post. The sad state of things.


Thanks for the feedback!

I clarified the point on Stripe a little. FWIW: Stripe is a.o. the company behind Sorbet[1], the Ruby type checker. A great contribution to the Ruby ecosystem.

From your examples, I only know Coinbase, and presumed they are primarily a Golang and React company, seen from their job vacancies [2].

Instacart, FlexPort and Gusto I had to look up. They are, indeed large, but not on my radar, because they are primarily US focused and -based. Thanks for correcting me!

[1] https://github.com/sorbet/sorbet

[2] https://www.coinbase.com/careers/


I'm not sure if declining Google search activity for Rails is the best metric.

Common consensus seems to be that Google results for coding-related concerns have gotten worse and worse in recent years, and I agree with that consensus. Are people avoiding Google, or avoiding Rails? Probably a little of both, I'd guess.

I think a mature framework like Rails will also tend to have a greater disconnect between "people searching for help" and "people actually using it."


> I'm not sure if declining Google search activity for Rails is the best metric.

Me neither. That is why I wrote the post and included many more sources, stackoverflow insights, Tiobe, rubygems.org, github etc. I'm sorry If I did not put this forward more clearly. The initial graph was mostly a hook, and not so much proof, as I mentioned in the first paragraph.


Thanks, I apologize, I clearly didn't read the article all the way through. Thank you for doing this work!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: