You have to remember in software development terms an SP design is / was preferred over a bunch of people who confuse a table in a Db with a table in word. People who make the other four and many more mistakes on a regular basis and don't even recognise them as mistakes.

A code first ORM compensates for that lack, it essentally replaces the SPs, and it does it in way that makes sense to the overall development process, when a database is simply Some where to store stuff when you application isn't running.

A few years ago I would have agreed with you without reservation, in some areas of software development I still would, but for the bulk of it, since the newer ORMs, not true anymore.