> you automatically invalidate one of ORMs biggest selling points which is being SQL-database agnostic 1. If the suggested alternative is writing only SQL from

> you automatically invalidate one of ORMs biggest selling points which is being SQL-database agnostic 1. If the suggested alternative is writing only SQL from the get-go, then why would one even care about database agnosticism? 2. A large part of SQL is compatible between databases, so this might be a non-issue. 3. You can always use specific in-database abstractions such as Views and Stored Procedures for those complicated bits.