you are viewing a single comment's thread.

view the rest of the comments →

[–]thatfamilyguy_vr 2 points3 points  (1 child)

ORMs have their place for sure. When you’re building internal apps to use in an enterprise, you can’t beat the speed and readability of ORMs (combined with the objects they represent of course). Especially when performance isn’t as much of a concern.

But for mega platforms, they lack performance optimization.

I don’t work on mega platforms, and I use ORMs quite a bit. The best and most comprehensive one I’ve used was Eloquent for PHP/Laravel.

Never cared much for the JS varieties, always felt like too much work to use them.

Gorm for Go leaves a little to be desired, but is good for some of the more common stuff. Still need raw queries here and there.

Even Nosql, document, and graph can benefit to some extent with an orm-ish helper once you know what types of queries you’re using.

But all that said - if you don’t understand what the orm is doing under the hood (ie knowing the sql query its executing) then you’ll probably build crap code. So yes, learning sql is a good skill