There are two things an sql lib must do to be very useful: prepared statements and mapping results. That’s enough.
There are two things an sql lib must do to be very useful: prepared statements and mapping results. That’s enough.
Entity Framework was the thing that made me spit the dummy with C#, uninstall Windows, install Linux and discover Go in the first place.
Knowing how to write good SQL is a superpower as a developer, and every time I've worked with an ORM fan I get this reinforced. "The database is too slow!" No, your SQL just sucks.
The parent comment made two claims: ORM not great (I agree) and “boilerplate reduction bad” which still needs some elaboration
https://bob.stephenafamo.com/docs/query-builder/psql/example...
https://github.com/stephenafamo/bob/blob/main/gen/bobgen-psq...
But the amount of queries that aren't fancy, and that an ORM is perfectly capable of abstracting away is (imho) 90% of all queries run.
Why make 90% or queries more tedious and error prone, just to make 10% slightly easier?