What?
looks like you don't really understand the power of aws/serverless/Kubernetes/kafka/cassandra/graphql/react. when your app becomes instant hit after featuring in the frontpage of HN, you will have 1 billion daily active users and your business goes into flames because of new workload.
I did 5 years of JS full stack development (both professional and for personal projects), until I decided to learn a more "boring" and mature language and framework. Never looked back and each day I love RoR more.
I guess it assumes we already know how to use the Ruby language, therefore it's a good option to choose for new projects?<p>I personally know near nothing about Ruby, other than read a couple of documentation pages.<p>Since I don't know how to use it <i>the right way</i>, I cannot take any side so I can agree or not with this suggestion.
When I understand something in Rails, it's wonderful, but the sheer quantity of "magic" in Rails makes it very difficult to deal with when you only touch Rails projects periodically.<p>I never had this issue with Java frameworks. I could drop into a large Java codebase almost anywhere and quickly get a lay of the land.
Rails fanboy since 0.9. Great framework. It's just such a ... comfortable? space to be in. Highly recommend it even after all these years - though now I use it mostly for modern SPA-style apps where rails simply provides an API. Which it is, yup, great for!
Started with Ruby in 2004, loved Rails until I switched away in 2015 as the jobs market was plateauing, and has stayed where it was. But it is fantastic and I’m back to tinkering with it using the fabulous new Stimulus Reflex stuff. The market is still rubbish, though, and there’s not enough good people out there.
I remember reading this a while back. So true <a href="https://medium.com/@timbuchwaldt/rails-is-boring-thats-great-f896e9ab2cb" rel="nofollow">https://medium.com/@timbuchwaldt/rails-is-boring-thats-great...</a><p>I am also very happystill to spin up `rails new` for every little side project