Not to mention, stored procedures mean having a DBA, or developer well versed in DBA, available when you want to make changes to your app, which isn't always an option.
Playing fast-and-loose with one's data is as bad as playing fast-and-loose with one's processing of that data.
Some DBAs are great though and bring experience that can be really valueable when building an app. Depends on how open-minded they are.
I see old-school DBAs as people you give logical schema to, and they make the physical schema fast and keep the system up. That role feels pretty dated.
Not anymore than writing SQL requires a dba. If you have developers writing SQL that cannot handle creating sprocs, then you already have a huge problem.
ORMs are a valuable abstraction. It's no good to go about your coding life without a care in the world for SQL, just because ORMs exist, but it's even worse to write an app littered with SQL, which is a language most likely entirely unrelated to your app.
1. I audited a code base for a friend a few weekends ago, and it was littered with SQL injection vulnerabilities, because the developer didn't like ORMs.
Sprocs also go a long ways towards preventing SQL injection. One could still build sql statements through concatenation inside the sproc I guess. /shudder.