Some advice to argue for GWT vs JSF

[Willie Slepecki]

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

[Thomas Broyer]

The new Google Sheets is powered by GWT. Would that help you?

(I've heard GWT is also used in other parts of Drive, and in Google Checkout)

[David]

Willie,

7-10 years is an eternity, even in my company we don't stick so long on one technology. With proper design you can make sure that the business logic can survive the technology you used. Nothing guarantees that JSF will survive and trive for so long. Look at SWING, AWT, Struts, it used to be a safe bet ...

The nice thing about GWT is that it is now fully opensource. At least, if it comes to that, you can grab the sources and extend it with what you need.

I tried to convince my employer to become an active committer, to make sure that we have the knowledge to fix things ourselves if needed, but for now I am not allowed. But I am still hoping for this because GWT really makes you productive and you can create really decent RIA apps with it.

For the same reason as you I decided not to go for third party widgets. I don't trust them to stick around, or to keep the same license forever. It's not the first time we need to factor out 3rd party widgets to avoid extreme licensing costs.

David

--
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-tool...@googlegroups.com.
To post to this group, send email to google-we...@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.

[salk31]

So it would have been totally safe to bet the farm on EJB2.1 because that is here for good? CORBA inside JSE!

[Dapeng]

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 ...