The Only Database Abstraction You Need

I actually came to the same conclusion on my own. I built my own little dynamic DNS client and from the start everyone was saying use an ORM at least on the surface. I went through what no where I'm does and I said what the F*** do I need this for I'll just write things directly in SQL as at the end of the day all my data is going to be ending up in SQL And sure enough festival did not disappoint. Very happy with my app BH. Thanks for releasing this video though and letting others know.

ORM have been misused for years due to improper knowledge of how to architecture an application.
Once you start to apply an hexagonal architecture pattern, you can concentrate database access in your DBAL (typically in Repositories) and adapt your use of the DB, either by using the ORM Query Builder or by writing raw SQL queries.
ORMs shine in how they allow to map relational data to objects.
If you add CQRS and separate commands from reads, you can quickly realize how you don't need an ORM on the read side but mostly on the write side.

SQL alchemy is a pain in the ass. Not because of it, but how people uses it to avoid learning or use SQL.

holy shit dude your video is full of false equivalences, cherry picking some bad ORMs, and saying "but some do this wrong!!!!! probably!!! right!!!!".
Did you need to make this video to feel better than everyone because you learnt how to type some SQL?

I can't remember the last time EVERY argument in a video was wrong, but this is it.

Totally BS video, ORMs could be pain in the ass that's true, but most of the statements are wrong if you just look at the documentation of any modern ORM

Dude, there is so much disinformation in this video. You should seriously consider making this private buddy. You tried too hard to make your opinions facts. In addition your lack of knowledge is apparent as almost everything you said against an ORM is false...

what is your opinion about EF core though? i learned sql before i stared using ORM's which allowed me to actually check how good the queries are it generates and its actually a pretty complete and performant ORM. (as long as you dont do stupid things ofcourse, but bad code can be written in any language)

There is a fourth, superior option: ORM with a Query Builder like TypeORM does it. I have done a ton of complex queries, that would be simply impossible with other ORMs and a pain in the ass to implement with raw dogging SQL.

World should be greatfull that you share your panifull exprience and wisdom with humanity.
Not all will take your advices seriously, many will argue or give you names but some they they will know.

I highly doubt all ORMs work as you describe it...