EF is a massive 'enterprise' codebase aimed predominately at SQL Server. If you don't need all the features ORMs like EF (or NH for that matter) offer (with all their associated config) then a micro-orm maybe better suited.
Dapper has been very useful at my current gig and more innovation in that space the better. Okay these micro-ORMs lack fundamentals like identity maps and caching but do you always need these features?
No, Dapper does not suck. I too have been using Dapper at our company recently and its been an incredible boon to our db performance and code readability.
Plus, if its good enough for the Stack Exchange team, then its plenty good enough for me.
Dapper has been very useful at my current gig and more innovation in that space the better. Okay these micro-ORMs lack fundamentals like identity maps and caching but do you always need these features?
Inertia is dangerous.