Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We are currently considering moving away from Entity Framework Core. Simple things work fine, but it generates ridiculous queries if stuff gets more complex.


Many ORMs are going to have trouble at some point when you start making more complex queries. I believe using an ORM well is largely in understanding the balance between when its tradeoffs are acceptable and when they are not. Per the other reply, I would probably start with EF Core in new applications, but would not hesitate to add Dapper or just plain SQL with ADO if I saw the need.


Is there any reason why it needs to be either/or, or are you suffering from OCD light like so many others of us? ;-)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: