I think that you can use SQL stored procedures with Microsoft's entity framework if you choose. Although we do not use the entity framework at the moment, we are rewriting our data-querying stored procedures to be more entity-based anyway, so a future fit should be increasingly straightforward (although we certainly have not resolved all the issues).
I think that article was useful for interpersonal relations, but did not really address the architecture of the information systems, the overview, separation of concerns and creation of an abstraction layer which will survive (with modifications) the expected lifetime of a system. Who (or more particularly, what role) is going to make those decisions? I don't see that as strictly a database administration or a database developer role, but as something over and above.