Re: Some advice to argue for GWT vs JSF

going pure GWT can never be wrong, if u want to play safe, make ur server talking only JSON/rest not GWT-RPC

by that u can later decided to throw away the presentation layer if another promising client framework should become popular

so far, java's tooling system is too good to give up ... 

On Friday, December 13, 2013 9:35:27 AM UTC+8, Willie Slepecki wrote:

My team just wrapped up an evaluation comparing gwt to jsf to be used in a new series of applications we are planning.  My team chose pure gwt over jsf and vaadin for a variety of reasons.  

Our problem is two of the primary decision makers are convinced that gwt is going to dilute and within 7 to 10 years be irrelevant and ended as a product.   Where did they get this idea?  A blog. Post obviously.  On the other hand, since jsf is part of jee, it's going to be alive and vibrant forever.  

I'm not asking to argue the validity of their claims  I already know why they say that and it's political, not technological.  What I'm asking is, can you help me come up with an idea to impress upon the other members of the selection committee that this idea is unfounded and gwt would be a safe choice?    I already. Have the vaadin report they generate, but that I fear isn't going to hold much weight.  

Maybe some records from red hat saying how many developers are dedicated to the project, estimated annual budget senscia is spending on gwt core development, stung like that is what these guys will care about.

Any ideas?  Thanks

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.