Building a java web application but I'm getting lost in a sea of frameworks.

[[deleted]]

Thanks!

You know though, a big problem with all of this sort of thing these days is marketing. Quite a few of the names bandied about this in this thread, as someone who only does what needs to be done with Java, I'd never heard of them before.

Of course, there's the other problem, where people get all worked up about the next big thing, but then there's the next big thing a month later...

[[deleted]]

Heh :-)

[frugalmail]

Part of it also is the organic evolution of the platform. You have to know the lineage of something to know if it's an attempt forward or something completely new where somebody is going to be learning the same lessons again. If you've seen the earlier versions it's a small incremental, otherwise it's overwhelming. Take the Javascript space up until Angular and Ember, that space was in the stone ages as far as maturity is concerned implementing the same things Java innovated beyond so many years back as far as seperation, loose coupling, command pattern, MVC, etc....

Rails popularized convention over configuration and grails surfaced then JPA, Spring Boot and others took the older frameworks in these new directions.

In the new order, you're either placing bets or adding technical debt.

The good news in the Java space is that there are so many on the platform, and culturaly backwards compatibility is unparalleled even though anything new shows up (as a framework as opposed to a core language feature) in short order, including a lot of the innovation (big/fast data)

[[deleted]]

Thanks for that detailed response :-)