{"slug": "entity-framework-core", "name": "Entity Framework Core", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 5, "commenters": 7, "warners": 0, "score": 5.003, "rising": 1.02, "first": "2025-11-26", "latest": "2026-10-18", "why": "EF Core is the gold standard for what I'd look for in an ORM", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 5, "neutral": 2, "compare": 0, "warn": 0}, "spark": [1, 0, 0, 2, 0, 0, 0, 0, 0, 1, 0, 1], "listed": true, "loved": [], "caveat": "", "short_quote": "EF Core is the gold standard for what I'd look for in an ORM", "kind": "", "icon": true, "domain": null, "github_repo": null, "official_url": "https://learn.microsoft.com/en-us/ef/core/", "pricing": "", "aliases": ["Entity Framework Core"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 802224689, "item_id": 50139043, "url": "https://news.ycombinator.com/item?id=50139043", "by": "jdthedisciple", "date": "2026-10-18", "stance": "recommend", "quote": "(DI, EF Core, ASP.NET Core...) so you still and up with proper architecture", "excerpt": "> The problem with AI SE is that AI writes un-architecture-ed code Not necessarily. I use SOTA models with established stacks like .NET which allow my agent to easily follow decades of best practiced patterns (DI, EF Core, ASP.NET Core...) so you still and up with proper architecture. In fact I can easily still manually inspect everything bc I already know how it's supposed to be written.", "context": "", "use_case": "data access", "switched_from": "", "story": "Show HN: Sphinx \u2013 A hook that quizzes you on your AI's code before shipping"}, {"id": 790208305, "item_id": 49388019, "url": "https://news.ycombinator.com/item?id=49388019", "by": "exceptione", "date": "2026-08-21", "stance": "recommend", "quote": "This is EF core", "excerpt": "`Included batteries` and type safety are not the only but imho surely the most important criteria for software projects (I am excluding throw-away code and scripts). The article raises an important point but fails to teach the reader about the JVM ecosystem and the .net core ecosystem. The standard libraries of these two zoo's of programming languages vastly eclipse what the discussed languages offer (Go, Python and ", "context": "", "use_case": "", "switched_from": "", "story": "Better Batteries"}, {"id": 753372848, "item_id": 47085803, "url": "https://news.ycombinator.com/item?id=47085803", "by": "wofo", "date": "2026-02-20", "stance": "recommend", "quote": "EF Core is the gold standard for what I'd look for in an ORM", "excerpt": "Thanks for taking the time! I love being able to see through abstractions too, but for web applications I'm looking for a bit more \"magic\" (e.g., .NET's EF Core is the gold standard for what I'd look for in an ORM).", "context": "", "use_case": "ORM for web apps", "switched_from": "", "story": "Farewell Rust"}, {"id": 749541505, "item_id": 46846344, "url": "https://news.ycombinator.com/item?id=46846344", "by": "CharlieDigital", "date": "2026-02-01", "stance": "recommend", "quote": "one of the best ORMs (EF Core)", "excerpt": "I started my career doing ~20 years of C# from pretty much the very beginning (JavaScript even before then!). Around 2020, I switched into the startup space and quickly picked up TypeScript since that's \"what the kids use\". It wasn't without struggles, but once I wrapped my head around TypeScript as \"shapes for JavaScript\", it clicked. At the time, the startup was undertaking a new product built on Nest.js[0] which l", "context": "", "use_case": "", "switched_from": "", "story": "The history of C# and TypeScript with Anders Hejlsberg | GitHub"}, {"id": 736885120, "item_id": 46055320, "url": "https://news.ycombinator.com/item?id=46055320", "by": "b0m", "date": "2025-11-26", "stance": "recommend", "quote": "We use newer Entity Framework (Core) in a few large projects with zero issues.", "excerpt": "We use newer Entity Framework (Core) in a few large projects with zero issues. Even have Dapper and moving away from it as it brings nothing to the table but strings and bunch of SQL.", "context": "", "use_case": "", "switched_from": "Dapper", "story": "Reinventing how .NET builds and ships (again)"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["data access", "orm for web apps"], "compared": [{"slug": "asp-net", "name": "ASP.NET", "co": 4, "switched_from": 0, "switched_to": 0}, {"slug": "dapper", "name": "Dapper", "co": 1, "switched_from": 1, "switched_to": 0}, {"slug": "net", "name": ".NET", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=50137950", "title": "Show HN: Sphinx \u2013 A hook that quizzes you on your AI's code before shipping", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49590656", "title": "Ask HN: Show your micro-SaaS", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49385068", "title": "Better Batteries", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47654062", "title": "Ask HN: Any Interesting Niche Hobbies?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47077383", "title": "Farewell Rust", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46782872", "title": "The history of C# and TypeScript with Anders Hejlsberg | GitHub", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 1}, "2025-12": {}, "2026-01": {}, "2026-02": {"recommend": 2}, "2026-03": {}, "2026-04": {"neutral": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"recommend": 1}, "2026-09": {"neutral": 1}, "2026-10": {"recommend": 1}}, "quotes": [{"id": 802224689, "item_id": 50139043, "url": "https://news.ycombinator.com/item?id=50139043", "by": "jdthedisciple", "date": "2026-10-18", "stance": "recommend", "quote": "(DI, EF Core, ASP.NET Core...) so you still and up with proper architecture", "excerpt": "> The problem with AI SE is that AI writes un-architecture-ed code Not necessarily. I use SOTA models with established stacks like .NET which allow my agent to easily follow decades of best practiced patterns (DI, EF Core, ASP.NET Core...) so you still and up with proper architecture. In fact I can easily still manually inspect everything bc I already know how it's supposed to be written.", "context": "", "use_case": "data access", "switched_from": "", "story": "Show HN: Sphinx \u2013 A hook that quizzes you on your AI's code before shipping"}, {"id": 794234916, "item_id": 49639682, "url": "https://news.ycombinator.com/item?id=49639682", "by": "littlecranky67", "date": "2026-09-10", "stance": "neutral", "quote": "EFcore, SQLite in the backend", "excerpt": "https://lockmeout.online Digital time lock service to boost focus and distraction free productivity sessions. * Generates as very long random password or pincode * You set this random combination as a password for your phone, social media account, wifi router or whatever * Close the lock and the code will be hidden until a timer is expired or countdown started * Given the length of the password you will have forgotte", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: Show your micro-SaaS"}, {"id": 790208305, "item_id": 49388019, "url": "https://news.ycombinator.com/item?id=49388019", "by": "exceptione", "date": "2026-08-21", "stance": "recommend", "quote": "This is EF core", "excerpt": "`Included batteries` and type safety are not the only but imho surely the most important criteria for software projects (I am excluding throw-away code and scripts). The article raises an important point but fails to teach the reader about the JVM ecosystem and the .net core ecosystem. The standard libraries of these two zoo's of programming languages vastly eclipse what the discussed languages offer (Go, Python and ", "context": "", "use_case": "", "switched_from": "", "story": "Better Batteries"}, {"id": 763103139, "item_id": 47693946, "url": "https://news.ycombinator.com/item?id=47693946", "by": "evklein", "date": "2026-04-08", "stance": "neutral", "quote": "data operations are handled with EF core", "excerpt": "Not really, but I'm happy to share more here :) In all honesty, under the hood it's a bit of a mess. I may have eschewed some of the software engineering best practices in lieu of building something quickly that I wanted. I'll get around to going back through and retrofitting the app with some cleaner code, but for now I couldn't even open-source it without a self-perceived hit to my portfolio. The project largely st", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: Any Interesting Niche Hobbies?"}, {"id": 753372848, "item_id": 47085803, "url": "https://news.ycombinator.com/item?id=47085803", "by": "wofo", "date": "2026-02-20", "stance": "recommend", "quote": "EF Core is the gold standard for what I'd look for in an ORM", "excerpt": "Thanks for taking the time! I love being able to see through abstractions too, but for web applications I'm looking for a bit more \"magic\" (e.g., .NET's EF Core is the gold standard for what I'd look for in an ORM).", "context": "", "use_case": "ORM for web apps", "switched_from": "", "story": "Farewell Rust"}, {"id": 749541505, "item_id": 46846344, "url": "https://news.ycombinator.com/item?id=46846344", "by": "CharlieDigital", "date": "2026-02-01", "stance": "recommend", "quote": "one of the best ORMs (EF Core)", "excerpt": "I started my career doing ~20 years of C# from pretty much the very beginning (JavaScript even before then!). Around 2020, I switched into the startup space and quickly picked up TypeScript since that's \"what the kids use\". It wasn't without struggles, but once I wrapped my head around TypeScript as \"shapes for JavaScript\", it clicked. At the time, the startup was undertaking a new product built on Nest.js[0] which l", "context": "", "use_case": "", "switched_from": "", "story": "The history of C# and TypeScript with Anders Hejlsberg | GitHub"}, {"id": 736885120, "item_id": 46055320, "url": "https://news.ycombinator.com/item?id=46055320", "by": "b0m", "date": "2025-11-26", "stance": "recommend", "quote": "We use newer Entity Framework (Core) in a few large projects with zero issues.", "excerpt": "We use newer Entity Framework (Core) in a few large projects with zero issues. Even have Dapper and moving away from it as it brings nothing to the table but strings and bunch of SQL.", "context": "", "use_case": "", "switched_from": "Dapper", "story": "Reinventing how .NET builds and ships (again)"}]}