Personally, I like Dapper because it gives me complete control over the SQL and is easy to use (well, at least for what I've been using it for).
For further actions, you may consider blocking this person and/or reporting abuse
Read next
The Evolution of .NET: Why It Still Matters in 2024
Soham Galande -
Leveraging Python's Pattern Matching and Comprehensions for Data Analytics
Alex Merced -
Collection and Record | Context of Oracle SQL
Pranav Bakare -
YARP vs. Ocelot: Choosing the Right API Gateway in C#
Odumosu Matthew -
Top comments (14)
Coming from C# definitely Entity Framework.
Now that I work mostly with TypeScript I would say TypeOrm
Not a major ORM, but I really like Peewee (in Python).
Now, I am using TypeScript and I write my own. I am tempted to try Mikro-ORM, though.
Tried TypeORM, but it disappointed me.
SQL builder only, like Knex.js is also good, but as you see, I am tempted to write an ORM, if it doesn't exist.
I enjoy a lot working with Entity Framework and Dapper, now that I'm coding in python kind enjoying SQLAlchemy.
SQLAlchemy it's easy to set up and start coding, don't have a lot of configs to deal or classes, but LINQ in Entity Framework with CodeFirst damn...
Hibernate! Because it's a suite of open source projects around domain models.
Dapper+1
eloquent is amazing.
JOOQ. Perhaps because it's not a ORM in traditional sense but rather a query builder (and extremely convenient one).
From the .Net/C# perspective I go with dapper and petapoco for simpler stuff but entity framework for the heavy ones.
I haven't used many ORMs but I really like Active Record with Rails!