IMO it really depends on the type of application you're writing, the statistical distribution between read and write operations and other factors, like the production environment, etc.
Both dapper and ef are just tools, to be chosen thinking at the big picture.
For most applications I generally agree with your point of view, ef readability and maintainability worth the cost in performances, especially if you put a sane layer of caching in front of your read ops.
There are other situations (low mem devices, simpler database structure and interaction, still want/need to use a RDBMS as persistence layer...) where Dapper represent a good alternative to raw ado.net.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
IMO it really depends on the type of application you're writing, the statistical distribution between read and write operations and other factors, like the production environment, etc.
Both dapper and ef are just tools, to be chosen thinking at the big picture.
For most applications I generally agree with your point of view, ef readability and maintainability worth the cost in performances, especially if you put a sane layer of caching in front of your read ops.
There are other situations (low mem devices, simpler database structure and interaction, still want/need to use a RDBMS as persistence layer...) where Dapper represent a good alternative to raw ado.net.