Earlier quoted context omitted.
True, but java carries a lot of legacy.
Java, or projects in Java? Java pretty much has to, in order to preserve the most important feature a runtime can have: backwards compatibility. Projects in Java are cursed from the beginning: the language has great constructs for boxing complexity (modifiers, inheritance, interfaces, generics, design patterns allowed by performant virtual calls, etc.). This means that when projects in other languages become unmanage…
The weird thing I always get with the always greenfield developers is how you know you aren't just creating even larger messes tomorrow vs the messes you're avoiding today. I guess it isn't your problem though if you're always working greenfield - it's someone else's.