Recent asp.net MVC experience has drastically reduced my .NET hate from the front-end/UI dev perspective. Is there anything similar in Java or does that servlet/portlet business which I only vaguely understand as doing something other than CGI for some sort of multitasking performance benefit always require tight-coupling to the HTML?
If not, what would I need to read up on to help write something in Java that makes this possible? Is some popular library the culprit?
Also, if these mysterious n-lets improve performance why do so many Java sites seem slower on load-time to me?
Struts, Java Server Facelets, more than I want to list out MVC, MVVM, and any other pattern that's hot at the moment usually has a Java version floating around somewhere with some degree of usefulness or utility (some good some bad as in every other part of the world).
Read up on Patterns and basic computer science. Maybe go the read a shit ton of RFCs route as its the road less traveled and will give you information beyond your wildest dreams and make you seem incredible to regular programmers. After doing this implementing decoupled systems such as MVC pattern will seem like simple work.
Many java sites seem slower on load time because of a variety of reasons revolving around 1) poorly administered 2) poorly coded 3) JSP compile time on first access (ie read up on how JSPs work).
Anyways, I hope this answer helps.