10 engineers on Hacker News describe using Entity Framework first-hand: 5 endorse it, 3 regret it, 2 are mixed.
“Because EF's default behavior implements Unit of Work, a LOT of the complex transactional spaghetti ended up disappearing when we switched.”
endorse · production · hirvi74 · 2026-02-02 · source ↗ · wrong label?“Because EF's default behavior implements Unit of Work, a LOT of the complex transactional spaghetti ended up disappearing when we switched.”
endorse · production · CharlieDigital · 2026-02-01 · source ↗ · wrong label?“With old EF we would turn off lazy loading... EF with wise use of .Include and no lazy loading is a pretty good ORM!”
mixed · production · rspeele · 2024-05-13 · source ↗ · wrong label?“so much churn with Webforms/MVC, LinqToSQL/various Entity Framework versions, all the WPF/WCF stuff”
regret · production · romanhn · 2022-06-01 · source ↗ · wrong label?“all the entity framework/ORM crap work that we do can actually be neatly represented as transforms”
regret · production · tejasv · 2020-12-05 · source ↗ · wrong label?“We used to show the new developers on the team a query generated by Entity Framework...23 pages long.”
regret · production · givehimagun · 2019-09-20 · source ↗ · wrong label?“I tried .NET Core with EF at a Hackathon and thought EF really went a long way. Had no idea about the restrictions”
mixed · personal · madeuptempacct · 2018-11-09 · source ↗ · wrong label?“I've used EF since it was first released, and we haven't encountered any major issues.”
endorse · production · 10 yr · manigandham · 2018-10-04 · source ↗ · wrong label?“things like async/await, Linq, and Entity Framework make developing Java web apps drudgery in comparison.”
endorse · production · manyxcxi · 2014-11-13 · source ↗ · wrong label?“I have successfully used EF with SQLite in production”
endorse · production · notJim · 2011-06-16 · source ↗ · wrong label?