I love ORMs. I recently wrote a little script to scrape a website and put some data in a database. I used Sequelize and it's excellent. I don't want to write an

INSERT INTO blah (A, B, C, D, E, F, G, ...) VALUES (a, b, c, d, f, e, g, ...)

statement where, whoops, I transposed two values! Will SQL throw a cryptic error because the types don't match, or will it silently accept my awful query because the types do match? Perhaps I'll find out after a frustrating night of querying data that doesn't seem to make sense.

"But post-it, why don't you write a loop that builds a query string?"

I could! But if I'm already abstracting away the misery that is SQL, I may as well use a library.

"But post-it, with an ORM I can't do <X thing to speed up my query>!"

I'm never going to need that. 99% of people using SQL are never going to need it. They're going to INSERT < 100 million things and then they're going to do a bunch of SELECTS and some JOINs and they won't care if the query takes 150 ms or 50 ms. And if they do, they'll optimize and write that one thing in raw SQL.