EF Core expression trees are nice, however, the change tracking behind the scenes are an absolute menace. I've gotten errors more times than I'd like, because EF Core had loaded a key in its store, and another query got the same key, resulting in an Exception because both touched the same record in the change tracker. Even if it was two separate requests.
I've become a purist sort of, using sqlc for golang, dapper for c# and sqlx for rust.
ORMs are 'fine' for simple crud apps, but once you go a bit deep in the sql, it becomes impossible to reason about. Telling an engineer that they can just run `explain analyze` on their query, and them having no idea how to actually reproduce their sql is not great.
This is also just my opinion, I've been in the same place, I used to love EF, but now I dread having to debug that stuff =D
Last time it was sending a non pointer to gorm in golang, panicing the application :,)