4 ms·
A lot of people say the same things about Rails. It makes you productive, it's incredibly easy to do things, things just work, etc. I have used Rails for most
by nullbytesmatter 5y ago
A lot of people say the same things about Rails. It makes you productive, it's incredibly easy to do things, things just work, etc.
I have used Rails for most of my career and for a number of side ventures. I have to say I have had a love-hate relationship with it.
I love everything people love about Rails (mentioned above). What I hate is how the speed and productivity comes back to bite you later.
The code eventually turns into a ball of mud and becomes near impossible to update. You have N-dependencies that depend on Y-dependencies of their own. Different Rails versions or module versions, and you can't update one without breaking something else.
You eventually live with it, and nothing gets updated but then you want security updates, and sometimes something terrible happens (like the mimemagic catastrophe) that forces you to ham fist updates together and live with some rails engines not working completely. But that's ok, because productivity right?
- jmarchello 5y agoI would argue that the problems you mentioned are not unique to rails. I've seen those same problems in other technologies and architectures, just as I've seen them in Rails applications. I think those issues come from lacks of carefully enforced standards, separation of concerns, domain design, and discipline. These are people problems, not technology problems. What rails provides is the freedom to think about your business domains and such without having to also design the plumbing. I would argue that rails gives you space to solve those problems, but you still have to solve them.