Doing Rails Wrong
bananacurvingmachine.com
Doing Rails Wrong
1–10 of 288 posts
Re: Doing Rails Wrong
#2Meanwhile in real production environments...
Rails apps are rare and getting replaced. Most web apps are static builds where the tools listed are not used all at once and largely irrelevant outside the dev environment.
> John runs a single command. The app boots instantly, working forms, instant loading times, blazing fast navigation.
Same with node? npm run build && npm start
Re: Doing Rails Wrong
#3nice
Re: Doing Rails Wrong
#4Meanwhile in real production environments... Rails apps are rare and getting replaced. Most web apps are static builds where the tools listed are not used all at once and largely irrelevant outside the dev environment. > John runs a single command. The app boots instantly, working forms, instant loading times, blazing fast navigation. Same with node? npm run build && npm start
Meanwhile in the real world - users do not care at all if it's a Rails app with refreshes or a React app. In most cases, the Rails app is actually better due to its simplicity.
Re: Doing Rails Wrong
#5Meanwhile in real production environments... Rails apps are rare and getting replaced. Most web apps are static builds where the tools listed are not used all at once and largely irrelevant outside the dev environment. > John runs a single command. The app boots instantly, working forms, instant loading times, blazing fast navigation. Same with node? npm run build && npm start
Meanwhile in the real world - users do not care at all if it's a Rails app with refreshes or a React app. In most cases, the Rails app is actually better due to its simplicity.
Users don't have to care and the result is exactly the same. That's my point.
Re: Doing Rails Wrong
#6[deleted]
Re: Doing Rails Wrong
#7I think there is a much-better-than-merely-non-zero chance that the rise of coding agents will also mean a rails renaissance. All of the complexity identified in the article really gets in the way of LLMs.
Re: Doing Rails Wrong
#8Ha, fun post, but these type of Rails posts would've been a bit more timely in 2015 rather than 2025.
Re: Doing Rails Wrong
#9This point has been made so many times. Know your tools and use the best tool for the job.
Re: Doing Rails Wrong
#10Meanwhile in real production environments... Rails apps are rare and getting replaced. Most web apps are static builds where the tools listed are not used all at once and largely irrelevant outside the dev environment. > John runs a single command. The app boots instantly, working forms, instant loading times, blazing fast navigation. Same with node? npm run build && npm start
The question I think we should be asking: Why? Why are we replacing everything with React and a bunch of other libs on top of it?
The front-end dev space feels like a cacophony of people all blurting out the same over-engineered stack. If your app is a few lists, a chart, and a form... Does it _reaaallly_ need React?
37signals is afterall running multiple successful products with Rails, and one of them is an email client.
I liked this video, maybe you will to: https://youtu.be/mTa2d3OLXhg?si=nhqGO4lPaAcP0mdm&t=3000
I don't agree with everything DHH says, but I think he has a really good point.