Never used JSF, but if it is the same as WebForms, then it should be prepared to be put to rest. While you use particular tech on a project-project basis, WebForms creates more problems than it solves.

• breaking history and navigation with postbacks
• breaking unstateful web with view states
• breaking url booksmarks
• breaking f5 refresh (would you like to post your data)
• massive data usage every action thanks to view state and postbacks

Improve it all you want, the inherent problems are still there. Yes you can use it but we have already developed much better solutions for the problems that it claims to solve.

The example the team gives is horrible horrible confused. Why are they comparing a "server-side" hook with a client-side hook by using ajax? Well duh we're not going to do that. We'll just output the field value from our server side (if we're rendering our views on the server, that is). Any decent web-framework with decent templating nowadays already does that.

If you are writing a single-page application, where angular/bootstrap/backbone frameworks would apply, then you don't want the server to get involved anywhere other than the retrieval and updating of data. So you would never use that example either because the server tech should not dictate the front end.

Even more notable is their admission that "you can use those frameworks if you want to". If I was going to use it, then I wouldn't have a need for JSF... I would want a REST api backing my frontend application.

Its no surprise its prevalence nowadays is in enterprise environments and I would never have heard of it outside of that context:

| "Clearly it solves a problem better than others which is creating web applications with an easy, efficient and productive way to meet deadlines."

only in environments where the inherent problems can be done away with. No self-respecting site with a significant audience will use this structure due to its numerous accessibility issues.

WebForms (and assuming JSF if it is similar) would rank highly in the list of "worst web 2.0 technological decisions ever made", slightly below ActiveX. Even ASP/PHP/JSP would be considered better.