ORMs Are Backwards
I have a lot of experience with the Django ORM, but no other.<p>So I disagree with most points.<p>The Django ORM does map pretty neatly to SQL (in my opinion), and especially Postgres. The migration tool is anything but &quot;half-baked&quot;. And I have observed that beginners have an easier time creating Django models than dealing with straight SQL.<p>On top of that, the Django ORM mitigates most SQL injection attacks out of the box, without even requiring the developer to know about SQL injections in the first place.<p>And the ORM enables elegant code reuse by constructing query objects that can be used in Template logic, Form validation, generic CRUD, REST endpoints and more.<p>I agree that most ORMs don&#x27;t help you with multiple programming languages. Though both the Django ORM and SQLAlchemy allow to customize a lot of the naming conventions and can be adapted to any legacy schema.<p>But then again: Is it even a good idea to access the same database from two codebases at all?<p>Some of the concerns about &quot;ORMs kill the SQL-star&quot; can be boiled down to a lack of a general understanding of relational databases in developers who learn to use an ORM before diving deeper into the philosophy of relational databases.