> Honestly one of the big problems I have getting into Java-the-ecosystem is the huge number of frameworks, tools, languages, etc that all compete with each oth

> Honestly one of the big problems I have getting into Java-the-ecosystem is the huge number of frameworks, tools, languages, etc that all compete with each other. Depending on how hard you look that is true for every language driven by open source: case and point is Javascript front end frameworks (Now the dust is settling a bit, and there seems to be Angular2/React/Ember, both with varying levels of overlap) Competition is a good thing. Choices are a good thing. What eventually happens is larger frameworks eventually emerge as winners, and absorb the good ideas out of the smaller frameworks. Spring Boot is an example of this. > The solution to every Java problem is just more: more tools, more syntax, more languages. That's the solution for 'Enterprise Consultants/Architects' maybe, but we normal java programmers just favor simple tools and jars these days. For example, I would roll over dead before I had to use Spring again, but I would much rather use some simple jars to stitch together an API like Jackson and Jersey, at worse, using something minimal like Dropwizard.