@lanodan @emacsen @xocolatl ORMs are great as long as you're just doing basic CRUD operations. Thankfully, that's 99% of the operations you'll ever need to do.

For the 1% of really complicated queries, that's when SQL will always be better because of how purpose build it is to return tables/do complex updates and deletes. You can do them in ORMs but it starts turning into a contortionist exercise at that point because even the best ORMs aren't made with those in mind. (Also for stuff that needs really optimized queries - ORMs may not choose the most optimal retrieval methods for a complex query.)

And *even then* it's all being bolted on top of some pretty awful design choices that should be changed cuz we've learned more about how to properly design a language since the 90s.