Re:Constraints in Go
by rad_gruchalski on Sunday November 17, 2024 @09:51AM
(#42164459)
I’m doing this job for 25 years and I haven’t seen a good orm. Sorry. Look, linq is nice. But linq is not enough of a productivity gain to switch the whole stack from go to .net. I used linq 15 years ago extensively and it feel like magic. But then again, how would you model jsonb select for a variable set of of properties and include nested or and and conditions using its notation? Maybe you could but how much longer is it going to take you rather than templating a string?
[ Parent
| on HN ]
Re:Constraints in Go
by marcus_holmes on Sunday November 17, 2024 @11:29PM
(#42169720)
I've been doing this job for over 30 years and I agree.
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.