4 ms·
> [0] Entity Framework has moved on a lot since then, and apparently now can be trusted to lazily load data To some degree. If you're using it for anything ser
by Quothling 2y ago
> [0] Entity Framework has moved on a lot since then, and apparently now can be trusted to lazily load data
To some degree. If you're using it for anything serious you're still going to help it along a lot. It's rather easy to do so, however, and I certainly wouldn't consider writing your own code as fast or easy as simply telling EF how you want it to do certain things.
I'm not an overall fan of EF. I especially dislike how it's model builder does not share interoperability with other .Net libraries which also use it. I also don't really like the magic .Net does behind the scenes. EF as a whole has been one of the better ORMs for any language since .net core. I'd still personally much prefer something like Rust's diesel, but whenever I have to work with C# I tend to also use EF.
- Foobar8568 2y agoDiesel is not an ORM and a typical rust library...
- kevthecoder 2y agoThe strapline seems to suggest it is an ORM (I've not used Diesel yet): >Diesel: A safe, extensible ORM and Query Builder for Rust https://github.com/diesel-rs/diesel https://github.com/diesel-rs/diesel
- to11mtm 2y agoYou might want to try Linq2Db, it is much closer to Diesel in how it works (More SQL DSL with parameter+reader mapper, less Unit-of-work ORM). FWIW, it can actually work 'on top' of an Existing EF Core context+mappings (i.e. if you have an existing project and want to migrate, or just need the better feature-set for a specific case.) or you can get pretty close to 'yolo by convention' depending on case. In general though it's a lot less ceremony to start messing around.