This is a good, solid assessment of what Rails 3.2 is like to work with. Like you, I don't totally understand where the animosity towards Rails is coming from.

This is a good, solid assessment of what Rails 3.2 is like to work with. Like you, I don't totally understand where the animosity towards Rails is coming from. If you want to make a drum machine that runs in your browser, like Giles Bowkett, then perhaps Ruby on Rails is really not good for you. On the other hand, if you want to earn a living, then the tremendous ease with which you can produce a reliable, secure, and full-featured application with Rails is really quite astounding. I do think that some of the criticism around the thick-client support in Rails is justified, however. Rails was ahead of the pack when it came to AJAX support in the early days, but it is not leading the way when it comes to thick-client architecture. At the same time, however, when the core developers announced that Rails would default to Coffeescript, half of the developer community freaked out, including many people here on HN. At this point, there are so many people with a stake in Rails it is impossible to please them all.