> It's wasted investment learning an ORM because its not knowledge that you can carry from project to project and throughout your career. OTOH, each database i

> It's wasted investment learning an ORM because its not knowledge that you can carry from project to project and throughout your career. OTOH, each database implements their own set of SQL features, so has their own SQL dialect. This is visible on stack overflow where the database name is a big component of the question / answer. I still agree with you though that SQL is superior to having a separation layer between the database. SQL is already supposed to be the human readable interface to a library.