Seems like most people are commenting in the context of web apps but I find ORMs are most useful on the client side (mobile/desktop apps) where objects can be l

Seems like most people are commenting in the context of web apps but I find ORMs are most useful on the client side (mobile/desktop apps) where objects can be long lived and you want to take advantage of ORM specific patterns like identity maps (https://martinfowler.com/eaaCatalog/identityMap.html https://martinfowler.com/eaaCatalog/identityMap.html) so you don't have multiple conflicting versions of an object in memory. If you're writing a web app and just pulling data from a database and dumping it to HTML or JSON then yeah it matters way less whether those database rows get materialized into objects before getting rendered to output, because you're throwing the objects out at the end of the request anyway.