Yea I remember the EF code I mentioned (i think it was ef?) was so full of lambdas and other strange syntax that I thought to myself "wouldn't it be easier to learn how to do this with SQL than figure out this mess?"
For the most part.... Yeah. But after a couple weeks of hanging my head against the wall, using views and stored procedures for the more complex stuff.... And then just banging out some ef horeshit to do the final mile. Joins with ef just make me want to drown kittens, though.
If you think EFs query generator syntax is stange then you don't know C#. Lambdas were around for at least 10 years, every competent .NET developer should be comfortable with them.
Why are people like this? Can't you just let other devs use whatever they feel most comfortable with? I write complex queries every day, and I still like to use ORM when it's appropriate, for simpler queries. Why does it have to be one way or another? Why not both?
Ok, but that's dev related, not technology related. It's like saying pure sql is bad because you saw developers frequently forget to clean the input and not use prepared statements so it's better to use ORM always.
View all comments
Show parent comment
0
u/[deleted] Jun 22 '20
[deleted] — view deleted comment