Hacker News Reader

Hey there's some selection bias going on there! Rails is great for consistency and even better if its your jam. Its stable and high quality and still headed in a great direction. Its a great choice. Especially if you can work in it long term, and pay its learning curve only once.

...but as someone using it in Anger for a few years now, I long for the day I can say goodbye to it and never look back, for all the usual reasons.

View on HN

I should say that I've not been using Rails _exclusively_ for that period. But it's the one framework that sticks around in my toolkit no matter what. It's what I reach for in any new project by default.

I was also using it in anger until recently, and I'm really glad I got out of it.

But I disagree that it's consistent or that it leads to consistency.

The "Rails way" or "DHH way" of building apps is indeed consistent, but most big teams eschew this in the name of more complicated (and less consistently applied) patterns.

It follows the Anna Karenina principle to a T. All good codebases are alike and follow the Rails way; each bad codebase is bad in its own way and uses bullshit like Trailblazer, Active Interactors, over-engineered Service Objects or some other bullshit. Sometimes all of them at the same time.

Reply on news.ycombinator.com