However, as with most languages, that is more a measure of the quality of the developer, than the quality of the language.
As a C++ developer now writing C# using .NET that new language and framework are a pleasure to work with.
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.
I can assure you that’s not correct, as I work in an enterprise that has plenty of unmaintainable COBOL still running, though they’ve supplemented it with lots of really bad .NET code more recently.