| I read the whole article, and I think there are good points and things I disagree with. The biggest counter point I have with those articles criticizing Rails for being "too magical" is to ask: what is the alternative? And I don't mean alternative in a sense that one developer will do something by hand. More like: what would you suggest a "medium-xxl" app company (author's words) do? Use another framework? Fair. But, as others have said, it is 2023 and even still most other frameworks still won't come close to Rails. Laravel is pretty close, Django as well. Next? I still miss Rails from 2009 (when I started learning it) when dealing with Next every day. Build some custom solution? Fair as well. But, how do you enforce standards over a big team? I used to work with Rails, then I went to work in a Flask app with multiple teams working on it... What happens in practice is, without a strong framework like Rails, each developer/team ends up creating its own little framework, with its own little quirks and ways to do thingz. And then when you need to maintain it, you need to learn a whole "new" ad-hoc framework, most of the times with no documentation and without the original developer to explain it to you. And the differences between what different teams/developers come up with can be drastic, completely different ways to do things. Rails is not perfect, but having worked with the alternatives for years now, I still think Rails got way, way more things right then wrong. I'm starting a side project now with Remix, Prisma and almost every day I still fondly remember how Rails had all of this setup figured out way back in 2009 when I started working with it. Almost any other framework/solution suggested, as the author said, for "medium-xxl" projects will have the same issues or even worse. To this day, almost every week I get myself thinking that I still wish there was a "Rails for JavaScript" (since I need to work with JavaScript). |