Taking A Poll: Entity Framework vs Others
-
I'm curious what percentage of you use EF vs some other ORM and why?
Also, how many "roll your own"?
-
Nuts to all of them.
<<< Rolls his own.
-
I'm curious what percentage of you use EF vs some other ORM and why?
Also, how many "roll your own"?
@Kevin-Marois said in Taking A Poll: Entity Framework vs Others:
I'm curious what percentage of you use EF vs some other ORM and why?
Also, how many "roll your own"?
In the past, I had to roll my own as most were not good: Working with SQLite in C# & VB
These days Dapr and EF Core are my go-to.
-
I haven't directly touched a database system in years, and it feels like my life has vastly improved accordingly. I don't need those problems anymore. I am not a firm believer in entity modeling in the first place. I think it has its place, but so often you're forced to adopt a one-size-fits-all framework that requires you to sometimes alter your data to match its limitations, or requires kludges in the alternative. At best you wind up with something that works, but could be a lot more efficient and less Rube Goldberg-like by the time you've applied say, EFCore to a real world dataset.
TBH, i've been out of the loop for a number of years, but I'm getting the impression that I'm not alone in my feelings on this, and that my viewpoint is becoming somewhat popular recently - at least inasmuch as abandoning attempting to ORM your data. Just query it. A lot of times, you don't need an ORM, and frankly, i think they only start to become relevant after your dev team and project reaches a certain size and level of remove.
-
I haven't directly touched a database system in years, and it feels like my life has vastly improved accordingly. I don't need those problems anymore. I am not a firm believer in entity modeling in the first place. I think it has its place, but so often you're forced to adopt a one-size-fits-all framework that requires you to sometimes alter your data to match its limitations, or requires kludges in the alternative. At best you wind up with something that works, but could be a lot more efficient and less Rube Goldberg-like by the time you've applied say, EFCore to a real world dataset.
TBH, i've been out of the loop for a number of years, but I'm getting the impression that I'm not alone in my feelings on this, and that my viewpoint is becoming somewhat popular recently - at least inasmuch as abandoning attempting to ORM your data. Just query it. A lot of times, you don't need an ORM, and frankly, i think they only start to become relevant after your dev team and project reaches a certain size and level of remove.
@honey-the-codewitch I agree with you assesment. I've always thought EF was over-engineeered. I have considered rolling my own, and I know I could do it, but there's so many shops using EF that you're really forced to learn & use it.
-
-
Not sure what you mean by 'rolling your own'? How about none? I've never needed an ORM for CRUD.
I'm now moving into .Net core and just about all the samples rely on EF.
BTW, what's theworst key ona keyboard tostartfailing? That's right, it's thespacebar!
In my opinion, they who think in terms of "CRUD" have lost the plot.