Rails isn't fun to use when you have to integrate with legacy systems and database schemas that doesn't fit with active record's way of organizing databases. F

Rails isn't fun to use when you have to integrate with legacy systems and database schemas that doesn't fit with active record's way of organizing databases. Far more work than necessary. When your database has simple things like checks, restrictions, foreign keys, pl/sql routines & weak entity tables built into the schema, active record completely ignores it and craps out when the db gives errors about it breaking your restrictions (it doesn't handle them as it does it's other types of errors). Even doing a db schema dump into migrations doesn't fit 100% and you have to recreate the entire schema in rails-pseudo-sql for it to work properly. Totally against the DRY principle. When your starting from a clean slate although, it's a different story. Then you can use rails conventions & restrictions and everything runs a lot more smoother. But if you got previous systems to build on, it's a bit more extra work. Rails is an opinionated asshole (like steve jobs), and when your not willing to back down, you got a lot of extra work to go through. Also sometimes rails is just too complicated or inflexible for the job and whipping up something quick & dirty in 500 lines of php would do you far far better.