Skip to main content

What's the future of the view layer in Java EE applications?

Java EE component libraries will continue to dominate
26% (64 votes)
HTML5, especially AngularJS, is and will be the dominant view layer
40% (99 votes)
Neither the front-end nor the back-end of Java EE will survive HTML5
6% (14 votes)
Mobile front-ends will be the only lasting view layer
5% (12 votes)
Some other technology will replace the view layer
8% (20 votes)
Java EE never had a significant place in the Java ecosystem, ever
9% (22 votes)
Other (please comment below)
6% (14 votes)
Total votes: 245

Comments

Re: What's the future of the view layer in Java EE applications?

On mobile, everybody prefers apps to mobile web sites. So one would think, this would lead to a revival of desktop apps, too. Anybody remembers applets? Time to resurrect them, let's program in great Java in the browser instead of Javascript. Bandwidth is sufficient, now, only the Java engine in the browser is no longer. Let's change that.

Re: What's the future of the view layer in Java EE applications?

There should not be any view layer in Java EE. Java EE should be a service-provider tier that any type of client (HTML, native, etc.) can communicate with.

Re: What's the future of the view layer in Java EE applications?

Pure client side rendering has its place but also many drawbacks, where security sensitivities are probably one of the most important issues, but unpredictable performance is a good second. So I do not believe server side HTML generation will go anywhere soon, but I'm highly in doubt if it will be JSF. More of the logic will move to the front end, and JSF is not well suited for that, but not as far as Angular.js wants it.