The whole "web dev tooling fatigue" is so real.
Doing Rails Wrong
11–20 of 288 posts
Re: Doing Rails Wrong
#12I knew it! I love tinkering like a peasant.
Re: Doing Rails Wrong
#13nice
Indeed as the poet Dwayne Carter once said, “if I’m wrong, there is no right/ and if I’m wrong, there is Snow White”.
Re: Doing Rails Wrong
#14That's a fun domain name.
Re: Doing Rails Wrong
#15Honestly I consider this title format to be click bait.
Re: Doing Rails Wrong
#16Ha, fun post, but these type of Rails posts would've been a bit more timely in 2015 rather than 2025.
The Rails development stack wasn't nearly as convoluted in 2015. A lot of this stuff leaked over from the JS ecosystem over the years
Re: Doing Rails Wrong
#17I sorely miss the sheer amount of utility that you can get from Rails out of the box for free compared to anything in the JS universe. Most JS devs don’t have the faintest idea how much they’re missing out on. Then again reinventing wheels is the JS way of life.
Re: Doing Rails Wrong
#18I think some people are so fixated with keeping up with the latest tech and prepare their project to scale infinitely that they have forgotten how good barebone setup is, especially with Rails. I get it, it's boring, unentertaining and might be understimulating to some. But it just works, Rails is truly batteries-included. Stop with the overengineering
Re: Doing Rails Wrong
#19Meanwhile 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 cl…
$1M ARR and 10k+ emails? Those are rookie numbers. There's nothing special about a rails app achieving that.
You'd be surprised what kind of far worse junk than anything we're talking about can scale the same or better and is ergonomic to another type of dev. This is all just bikeshedding.
Re: Doing Rails Wrong
#20I agree with the sentiment on this. I'm building applications that are easily converted to native mobile apps with minimal code and engineers left and right are telling me I should use 60 different libraries and frontend tools to reach the same goal.
Meanwhile Rails is becoming easier and easier to run complex apps with much smaller teams.