That would eliminate it for me.
Not everyone is coding APIs and fat client web apps. I'd prefer a framework geared up to do standard web apps as well.
That would eliminate it for me.
Not everyone is coding APIs and fat client web apps. I'd prefer a framework geared up to do standard web apps as well.
I'd be including a consideration of AngularJS, Backbone, Ember etc. + a service-oriented backend framework like Dropwizard. That's also incidentally how you'd architect your backend support a native mobile client, which is a good thing to prepare for even if you think you only need an HTML frontend right now.
https://dropwizard.github.io/dropwizard/manual/views.html
Don't forget that old style web apps are basically REST frameworks that render content with a content type of text/html...
They really aren't. A REST API wants to be simple and orthogonal; if you want two different pieces of data you make two different calls, so they're well suited to the "one controller per URL" paradigm. A traditional web app needs to combine and reuse components on every page (e.g. you might have a "messages" widget or a "user info" widget, which you would want to be encapsulated with their own logic), so you need better support for composing together different pieces of logic, and a single controller no longer makes sense.
JSF it is :(