At times too much magic, like queries mysteriously failing because you have a dangling "navigational property" without a database column. That one was a hell to debug.

At other times, too little control over how the query is translated to SQL, or DB features not being exposed. With time the frustration piles up..

EDIT: I'd be OK with a light-weight ORM, like stuff these columns into these fields of that class. Leave the rest to me. Though EFCore got a bit better with support for query types so I can map classes to views / stored procedures and do the "real" work there.

Compared to writing Sql stored procs it feels really hard to write something that spits out efficient sql.

You can't run (as far as I'm aware) things like query analyzers like I can with SQL to get execution plans.

It can be an absolute nightmare to debug. Like proper hell that where you can lose a day or so over something that ends up being stupidly simple.

I hate it and would choose just doing SQL with a plain ORM anyday over ever touching EF again.

When I was using it it also had poor support for immutable types. I imagine this has got better.