Hi there, I hope to get here an advice about a question I'm afraid is asked very often...
At the moment, only production ready, viable alternatives we found are GWT (and frameworks under its umbrella) and JSF (which despite a not so good fame, is a Java EE standard), and we are evaluting both of them.GWT has got at least a couple of features that makes us willing to adopt it, and among various GWT implementations, Errai has the advantage to be under Red Hat / JBoss umbrella, so we think it will integrate better with Wildfly and / or other JBoss products.
Moreover, Errai authors seem to have a clear idea about where their framework is going, which is its roadmap, and so on.
This said, we have a big concern about the sustainability of choosing GWT for the foreseeable future. No one has a crystal ball, of course; nevertheless, it's worrisome that current GWT release (2.8) is still in beta, after more than an year after the last stable release. So, first we are literally scared that, at a given point, GWT will disappear dragging with itself all related frameworks. It would not be a problem in itself - one may go on using the latest stable release - but GWT is a "mediator" (let me define it so) between two worlds, Java and the browser, both of which aren't going to stop enhancing and evolving over and over. If GWT stops evolving, later or sooner it will be incompatible with next Java / browsers releases.
As a second concern - as the first wasn't enough ! - we're seeing that ALL gwt frameworks are moving from Widget to embrace WebComponents like Polymer. Doesn't seem a little difference: with web components, would the developer still be able to write custom components and using Java all over the project, to handle events and GUI layouts and so on ?
How would Errai survive (and project based on it) in the case of GWT being abandoned ?
Thanks in advance to everyone and, please, forgive me if some questions seems "nasty"....