Comments by "justanothercomment" (@justanothercomment416) on "DONT USE AN ORM | Prime Reacts" video.

  1. The amount of tedium for result to internal representation cannot be understated. A good ORM provides much more than mere type safety.
    1
  2. Correct. A good ORM handles schema, migrations, and easily allows EXPLAIN for the generated SQL. SQLAlchemy + Alembic is an amazingly good combo. Like any tool one has to learn it to be effect. But... An ORM is not a replacement for knowing SQL. To effectively use an ORM you also need to know SQL. Otherwise, how can you verify it's properly and efficiently doing what you believe you asked it to do? A large number of complaints with ORMs is people believe they don't need to understand the underlying technology. It's a skill issue.
    1
  3. Good ORMs will also create your schema and provide migrations. If you use an ORM you also need to know SQL and how to explain the generated SQL and validate it's doing what it's supposed to do. An ORM is not a replacement for learning SQL. It's simply not honest to complain about an ORM if you don't know what it's generating or doing under the covers. I've done a ton of SQL and ORM. For most common use cases ORMs are the way forward. Don't allow skill issues prevent you from learning your tools and using them properly.
    1