> However, as with most languages, that is more a measure of the quality of the developer, than the quality of the language.

No, it’s more a measure of the quality of the development organization and process. The quality of individual developers is a factor here, but not the only one and often not the limiting one on software quality (and particularly often not on, e g., whether or not business requirements and system design are documented in a useful way to support maintenance and change analysis.)

There are lots of fairly common institutional factors at the kinds of shops that also tend to have lots of COBOL legacy code still running which also tend to result in instant-legacy code independent of platforms. They also have common in institutional patterns that tend to have platforms like Java and .NET.

This is not an indictment of Java or .NET as platforms, or of the individual developers in those environments.

Quite right — and to the extent that the blame goes to any individual developers, that comes back to the organization: do they pay well, offer a good working environment, etc.? One bad hire, sure, it happens but if it’s repeating that’s structural.