[dragonwriter]

> But once things go "enterprise" and much of your ongoing development gets outsourced, and it will, all bets are off.

That has nothing to do with language; Java for which development is outsourced and maintenance goes in house is pretty much a nightmare, too.

But that's pretty much a "myopic development practices -- including outsourcing development of code you are going to need to end up supporting in house -- will blow up in your face problem", and not an issue relating to any particular language or platform.

Chances are, if you have the authority to make enterprise-level language/platform policies, you also have the authority to make enterprise-level decisions on whether and when to outsource development of software, so it makes sense to just do the latter right than to make an otherwise second-rate choice on the former to make up for doing the latter poorly.