Web frameworks are sometimes compared using their components and L&F as main criteria. Visual appeal as a differentiator, however, is not critical for productivity. Before you are going to look at the components, you should rather more deeply think about the user interactions.
In case your application consists of a set of wizard-like forms (page flow) with validated input fields, data binding and server side validation will increase your productivity and reduce the complexity of the application.
On the other hand, office-like applications with longer "offline" periods do not require fine grained interactions with the server and can live entirely at the client side.
Server-centric frameworks keep a component UI tree on the server. The state of input fields and UI components are synchronized with the server side representation for your. Usually you get data binding for free and can easily perform server side validations as well as, access any backend services. Serverside validation is implemented in Java and is easier unit testable. In addition, client side validation can be implemented to avoid server round trips.
The strength of the server-centric frameworks is built-in fine grained data binding and server side validation as well as conditional page flow. Naturally a server side framework is less convenient to build offline, office like applications with a considerable amount of client code. JavaServer Faces, Wicket, Tapestry, Vaadin are some examples for server side frameworks.
Because a server-centric framework is going to be executed on the server, it will consume a considerable amount of CPU and memory.
See you at Java EE UI Workshop at MUC Airport!
Web Apps, SPA, PWA with vanilla Java Script (ES 6+), CSS 3 and WebStandards only. As simple as possible, but not simpler. See you at: (Progressive) Web apps, Single Page Apps and WebStandards airhacks workshops at MUC airport, Winter Edition
airhacks.fm the podcast:
Stay in touch: airhacks.news.