The only big problem with ORMs is when developers are allowed to use them to construct database schemata.
As long as you have a not-crazy person in charge of the initial design, you can allow—and even encourage—developers to make versioned changes to the database.
If you let us start from scratch with ORMs, it will suck for everyone.
There’s a fundamental mismatch between what developers think of as objects and how relational designers think of tables.
ORMs can smooth that over. But nothinking can undo the wrong-headed-ness of a developer thinking of a relational dB as an object store.
As long as you have a not-crazy person in charge of the initial design, you can allow—and even encourage—developers to make versioned changes to the database.
If you let us start from scratch with ORMs, it will suck for everyone.
There’s a fundamental mismatch between what developers think of as objects and how relational designers think of tables.
ORMs can smooth that over. But nothinking can undo the wrong-headed-ness of a developer thinking of a relational dB as an object store.