| It's hard to counter "it sucks" and other rather vague points like the ones you've made. > upgrading to newer versions of RoR sucks This hasn't been my experience at all. Rails comes with a built-in tool that interactively helps you upgrade your app `rails app:update`. Even on a 300k+ line Rails app I work on, our last major Rails upgrade took a single engineer about a week to do. It could be better, but it's one of the easier frameworks to upgrade, in my experience. > The more time I invest in trying to like RoR the more I end up having to fork gems to patch them because upgrades cannot be made smoothly Isn't this the case generally? Dependencies are liabilities. Not sure why this is a problem with Rails?! > It so easily integrates ActiveRecord, and heavily encourages it, that when you want to pull out of using it it’s a huge pain. ActiveRecord is a central component of the Rails framework. Why would they encourage you to use an alternative? > Test suite combines unit and integration testing. I think it's first important to state upfront: there is no single canonical definition of "unit" or "integration" tests. I assume your point is that the standard unit test examples in Rails hit the database? That being bad is, like, your opinion, man. And you totally can decide to not design things that way. |