What a ridiculous statement. You can be excited by new tech and realize how it can solve your problems.

New languages lack most of what is needed to be highly productive. Tooling is minimal to none. Libraries are sparse and still catching up, this takes many years. Many gotchas remain undiscovered and will bite you in production.

To get actual product work done with optimal efficiency, a mature ecosystem will always win.

And you can be maintaining a system built by developers who got excited by shiny new tech and made a load of inappropriate technology choices because they were flavor of the month and looked good on their resumes.

It sounds like you've had bad experiences with some devs and you're applying that to everyone.

Maintaining a codebase written in C is far far harder than one written in Java and that's far harder than one written in Go.

I have worked in tech long enough to see some common patterns. It's usually intermediate devs (though not always) who get excited by new tech. The same people are usually pushing to use shiny new tech in places where it isn't needed. You don't get cynical old school devs trying to replace working parts of the tech stack with tech less than 5 years old.

Personally i think developer skill has far more to do with maintainability than language choice. And I have worked with a lot of shit code.