That culture is the same regardless of the language.

The famous Design Patterns book is for enterprise projects based on Smalltalk and C++.

CORBA and DCOM were a thing a few years before Java was invented.

And so forth.

Not really no, you can't just ignore the culture context of languages.

Ruby projects are going to have a better testing coverage and culture in average than Python projects whereas in reality both languages could do the same.

Java overengineer culture is still present despite being non-existent in other languages like Go whereas in theory it could exist in both.

Nowadays you can do anything with any language, in practice the culture often goes in the way

Ruby is hardly a thing in enterprise computing, and until AI craziness, the only thing that Python mattered for enterprise shops was system administration instead of dealing with a mess of shell scripts and Perl.

Go culture has brought us YAML spaghetting and kubernetes madness at enterprise level.

There's a very large world outside the "entreprisy" companies you are used to let's say...

There is, however the subject here is enterprise culture, so lets not move goalposts.

I don't, I see the java type enterprise culture itself as a downside.