> In short, the causation is backwards - folks who want to or enjoy making things more complex end up using Java more often. That is complete utter nonsense. D

> In short, the causation is backwards - folks who want to or enjoy making things more complex end up using Java more often. That is complete utter nonsense. Developers most likely use Java because 1. they have to which is the case for Android or using existing libraries/code base or 2. because they already know it which is typically caused originally by number 1. 3. The language is still one of the popular language so for many it is a safe bet. As for ShoelaceTyingStrategyFactory... I have seen that crap in Typescript, I have seen it in C#, I have seen it in Objective C... Its caused by complex annoying needless requirements. See what happens with Java can happen with any language where you are don't have a proper development process of removing needless requirements. You end up with complexity. And yeah sure some people enjoy solving complex things and making it scale but the neither the language nor the community caused that. Now if you are talking about the spec writers like the JSR authors... yes those guys actually had it in there interest to make it complex because their company would be the only company that could make a reference implementation (for example Day software with JSR 283). But this is not the Java developer community as a whole.