Entity Framework Core

“the static typing benefits of them in C# makes ORMs very valuable when used appropriately”

“writing db queries in Python is just plain pain compared to C# + EF”

“in EFcore lazy-loading and auto-navigation is not on by default - you opted in at some point”

“These days I just use EF with Sqlite on 99% of my projects.”

“EF works fine with SQLite for a project I work on.”

“EF Core is so easy to turn into a disgrace for performance, developer experience, AND build times”

“Had they not open sourced EF, it could turn into an existential threat to the project.”

“ORMs simply cannot cope with provider specific requirements”

“EF seems to be the easiest way to shoot yourself in the foot”

“The real win in EF Core 11 is pruning the reference-nav joins out of split child queries”

“I have found a lot of the anti-ORM critiques come from either using a crappy ORM”

“I go and look up that function in the EF Core docs and learn by reading the docs”

“EF is solid and proven. Easy, low-lift type safety end-to-end from DB up with very good perf.”

“EFCore is still the best ORM I've ever used, with full support for SQLite, Postgres, MySql, etc.”

“You barely need any dependencies other than aspnetcore and efcore for most applications and your AI knows them well.”

“It supports bfloat16 but... the SQL client doesn't! Or Entity Framework.”

“creating some strange predicates in SQL that end up being unable to seek into string indexes”

“it vastly increases productivity and reduces bugs”

“e.g., .NET's EF Core is the gold standard for what I'd look for in an ORM”

“a LOT of the complex transactional spaghetti ended up disappearing when we switched”

“EF makes the 90% use case easy and the 10% case possible with very little pain.”

“I have never used any ORM that is as capable. Entity Framework Core with Linq is what keeps me on .NET.”

“nothing right now compares to the power and DX of EF Core + Linq methods”

“Massive productivity boost, and LINQ rivals SQL itself”

“ended up being a tightly coupled mess from IQueryable being passed around”

“let it do the simple stuff and if you need anything more complicated than .Include write the query yourself”

“We use newer Entity Framework (Core) in a few large projects with zero issues.”

“I like the tighter code, but you definitely do need to keep your eye on the "magic" of EF”

“ef core is great for simple queries and modification of your data while using the changetracker”

“We are also running into more and more performance issues with EF.”

“their pursuit for performance is relentless (e.g. see Kestrel and Entity Framework evolution)”

“you’re writing your app in Entity Framework as much as you are writing it in C#”

“eventually you wind up building your project in Entity Framework just as much as in C#”

“LINQ plays well with the same static analysis tools as the rest of C#.”

“This mostly works, until it doesn't, or it does but has strange generated sql and performance.”

“EF Core is amazing -- in it's default setup it works for 99% of situation.”

“I found it completely illogical for my ORM to maintain state.”

“It's trivial to make efficient projected queries with ORMs like EF.”

“my productivity has increased substantially since I tried EF for C# and Drizzle for TS”

“you get a lot of help from your editor that you wouldn't get when writing SQL”