[scarface74]

It’s not just about EF. The beauty of C# and Linq is:

Linq => expression trees => provider => native query language of data source => data source.

Written correctly, you can pass expressions around like:

repo.Find(c => c.age > 65 && c.gender == “male”)

And the expression can be interpreted at runtime by either EF creating native sql or the Mongo driver creating a native MongoQuery or even an in memory List for unit testing.

No matter how good another ORM may be for another language, what made C#s implementation better was Linq + expression trees.

[royjacobs]

Except EF is basically the only provider that works 100% robustly. I have some pretty bad memories of getting NHibernate's Linq provider to work correctly, since it would just randomly mistranslate queries or flat-out throw exceptions.

[osd]

As someone who has switched almost entirely away from .net to go, this is absolutely untrue. I'm fairly certain the issue was PEBKAC

[scarface74]

The Mongo Linq driver is excellent. It’s not exactly an ORM, but it does let you work with strongly type collections and the queries it produces are pretty good.

There was also another Linq/ORM I used back in the day for Postgres. I can’t remember the name of it.