3 ms·

Moving fast is often crucial, but you typically also get more readable code, which is also worth it. A query/DML that is badly optimized is usually very comple

by jasfi 2y ago

Moving fast is often crucial, but you typically also get more readable code, which is also worth it. A query/DML that is badly optimized is usually very complex, which means that the ORM's syntax isn't a good fit. No problem, since they typically support raw SQL calls, so nothing is really lost. You just have to know when to use the right tool for the job, as always.

throwaway19972 2y ago
> Moving fast is often crucial, but you typically also get more readable code, which is also worth it. I think the exact opposite is true, actually—because of the introduction of stuff like lifecycle hooks it becomes very difficult to figure out how the domain semantics translate to query/execution semantics. Of course some are lighter than that and just e.g. map a table to a domain type (which is much more readable), but that's not typically what catches criticism.