> It does have a migration system but rather than doing model agnostic queries it just references the original models, which leads to problems when setting up t

> It does have a migration system but rather than doing model agnostic queries it just references the original models, which leads to problems when setting up the database in development mode since you can't just run all migrations. That's true and this has caused problems before, but there are at least two potential solutions that I've used (none of which are typically referenced in tutorials etc. of course): 1. Write your migration in SQL (ActiveRecord allows that - and in some cases it's even necessary) 2. Copy your model classes into your migration file, namespace them and reference those namespaced models in your migration. > ActiveRecord is arguably what killed Ruby for most webapps and I can say that pretty confidently. I don't particularly like ActiveRecord, but do you have any particular evidence for this assertion?