3 ms·
Nowadays in Rails-land there's lots of tools to manage that, [the latest](https://blog.saeloun.com/2020/02/25/rails-strict-loading-mode-to-fix-n-1.html https://
by gosukiwi 5y ago
Nowadays in Rails-land there's lots of tools to manage that, [the latest](https://blog.saeloun.com/2020/02/25/rails-strict-loading-mode-to-fix-n-1.html https://blog.saeloun.com/2020/02/25/rails-strict-loading-mod...) integrated into Rails itself.
ORMs can be bad, but it's not fair to blame them "just because".
- whakim 5y agoI'm not so sure. My experience is that ORMs often discourage (or at least lessen the need for) getting a good grasp on databases and SQL because they abstract away a lot of fundamentals. Like any abstraction, there are obviously benefits too, but I do think it's reasonable to say that "makes it too easy to write sloppy/unperformant queries" is a real cost.
- gosukiwi 5y ago> My experience is that ORMs often discourage (or at least lessen the need for) getting a good grasp on databases and SQL I agree knowing SQL is very important, even if you use an ORM, sometimes you might need to roll up your sleeves and write some SQL (not to even mention knowing how to EXPLAIN queries, use indexes, etc). Nowadays most things are abstracted away. A similar thing happens with IDEs, if your IDE takes care of compiling and building everything for you, then you don't understand how everything works under the hood. Is that a bad thing? It depends. If you show HTML to a junior JS dev he'll say it's React, lol. I think there's no way escaping the abstractions in modern times.