This is one of those, "in theory, there's no difference between theory and practice. In practice, there is" issues.

In their, quality software can be written in any programming language.

In practice, folks who use Python or JavaScript as their application programming language start from a position of just not carrying very much about correctness or performance. Folks who use languages like Java or C#, do. And you can see the downstream effects of this in the difference in the production-grade developer experience and the quality of packages on offer in PIP and NPM versus Maven and NuGet.

That's not a fair comparison. In your example, you're talking about the average of developers in a language. In this situation, it's specific developers choosing between languages. Having the developers you already have choose language A or B makes no difference to their code quality (assuming they're proficient with both)

> In practice, folks who use Python or JavaScript as their application programming language start from a position of just not carrying very much about correctness or performance. Folks who use languages like Java or C#, do.

Nonsense. Average Java/C# is an enterprise monkey who barely knows outside of their grotesque codebase.

> production-grade developer experience

Please, Maven and Gradle are crimes against humanity. There's a special place reserved for Gradle creators in hell for sure.

The "production-grade" developers should ditch their piece of shit, ancient "tooling" and just copy uv/go/dart/rust tooling.