I 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

I 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.