No argument from me on the deployment issue... deployment with Rails is a massive pain. However, the guy's other points were mostly pretty small things. I mean, yes, it is annoying that it can't auto-discover foreign keys (either by using the RDBMS's data dictionary or by using naming conventions the way that it does everything else). However, it's really fundamentally NOT that big of a deal. Once you've told it what your fk relations are, a lot of nice functionality magically appears for free.

Similarly, okay, yeah, so it has its own standardized naming conventions for tables and columns that differ from the dozen or so other different naming conventions out there. It's *really* easy to manually override any of the conventions- like one line of code easy. Again, fundamentally NOT that big of a deal. While I'm in full agreement with the author that the documentation on this particular point needs work, I do have to say that it's about five seconds worth of Googling to find out all you'd ever want to know about what its conventions are.

Most of his other complaints are workflow-related— when one is learning how to use a new system, a certain amount of hassle (including a false start or two) is always involved. The question is primarily one of how long it takes to get past the initial awkward phase, and how much of a productivity increase is seen once you do.