Ruby on Rails

I understand what you are saying, but this is not correct. I know of a company that runs on Rails that is *heavy* into SQL for optimization. What you said could be applied as much to Rails and ActiveRecord ORM as it could be to Hibernate, EclipseLink, etc.

I think this whole topic of Rails bashing is a bit misguided. I worked in Java for many years and Ruby (CRuby/JRuby/Rails/Sinatra/etc.) also the last several years, I can say that there were definitely periods of time where I've wanted to bash my head into my desk. But, if you stick with it, it will treat you well.

I also see some are complaining about having to do things "the Rails(tm) way". Sure, it makes things easier, but it doesn't stop you, and in the case of legacy integration (we run alongside a substantial Java service-oriented environment that's fairly complex along with other legacy apps/services/webapps), I just wrote some gems to handle things that we needed, so others in the same situation won't have to go through as much trouble:
https://github.com/garysweaver?tab=repositories

Of course, the first thing to do is to search around and make use of what others are already offering. Keeping up with that is more difficult than almost any other part of my job. :)