GWT advantages

[Navindian]

Hi

 

We have decided to go with GWT and dropping the option of JSF for google maps application. I need to prepare a slide to support the same. Please suggest the parameters where GWT passes and JSF fails. It should be very generic such that Quality people appreciate it.

 

thanks

navajyothi

[Thomas Broyer]

JSF is a failure per se, so it shouldn't be hard to find arguments there (you don't have to search long on the web to find many). Not only is it a failure, it's a mistake and an anti-pattern.

Besides that (statefulness, anti-Web-style, etc. of JSF), the main difference will be that GWT (any "full AJAX" app actually) moves the UI work to the client, leaving only (mostly) business things to the server; similar to client-server (where the browser is the client) vs. mainframe (where browser is the terminal: dumb, doing almost nothing more than displaying what the server built). Implications on the server computing time and memory usage, and the network load is huge.

Basically, JSF is Web 1.0 and GWT is Web 2.0.

[Dennis Haupt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

what about telling them why you chose to use the GWT? :)

as someone who just worked on a google maps integration (for 2 month)
using the GWT, i would say that the GWT gives the programmer a lot
more "power" in general, development speed and possibilities to debug
everything than any other technology that runs on the client that i've
seen so far.

> -- You received this message because you are subscribed to the
> Google Groups "Google Web Toolkit" group. To post to this group,
> send email to google-we...@googlegroups.com. To unsubscribe
> from this group, send email to
> google-web-tool...@googlegroups.com. For more options,
> visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.

- --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOpFqoAAoJENRtux+h35aGSYQP/0yciaOpU/JhI/tocmeBASTD
MfVIBzUfwYgDpwZPSuZvHi12OKLdqo36VpPsJpgeSaemowMBn2rAUWQmfc5/9sVt
5+u0dXo/+BlepS5AE3VHaCKHBHJWG6+UV/7jA151yvEmbXd6iFpVq9y4P69+hjb1
K3vauIH0NkNb0QKNcvSZwEbhfTzehY2wHFRQ5481T1QFv4vT4rsoeJ4kvk1Iarsg
KO1syyuJrRqNGnjhU97ga8zhtgLt23/lISOMgG7ykY7CXz6l2FuqBZ/NWsVzG+M/
5J4AECBmoRU1BTfO8E8o43DX0JqOQAB+MhgrGCaX3EIAbp1VBpLZdZ6eKMifce1F
4gRGiKThCmWedHoDeN8utDN7DKab2J7+R547dcqhIg8M1z64tqd0AQOutyhmkuis
d9LKgA1We5R/MDTwJUFwu/qL+8ORxPfg2HwhBbCNv0BzHBrjh7Cmxm/ZtNr0YP2K
QVPyZCjbOgl9Eq1Nsg3z4UaYu5LJT66tci46AGgc4KbqhOw9ylc/5ubiSDRNgE6U
lESQYPrIXdRsJTRuUNuzy1KEkLikPNcLFwB5WK7GOTUZfET2pyk2DWV4IKzd7ltQ
7afOBO1hCoO/U9LzEdwOT8lFPy1HRVGJdA0oNBUpE6k3rBDOzlS6+kJ6AuC3X915
R9F9U+AsP0tMF6ESmzja
=Zfsk
-----END PGP SIGNATURE-----

[Roger Studner]

As someone who uses GWT, but also knows HTML/CSS/jQuery… I will at least honestly (flames expected) say that developing with GWT, while great for 'java devs' is far slower and more painful than just doing traditional html/css/js development (if you know what you are doing that is)

Roger

[Thomas Broyer]

This is not surprising. But GWT is all about reusing code with your server and/or other Java clients (e.g. Android), and benefiting from the Java tooling. Java also brings static typing, which some people prefer.

[Robert Zaleski]

It's funny to me that you feel this way, because every large project I've worked on using a dynamically typed language has turned into a rats nest and has caused me undue headaches with me having to maintain the runtime context in my head instead of having that determined for me.  I'm talking about once you get into the 30K plus lines of code.

I do think that if you're just adding a menu or some other JS glitz to a page, GWT is definitely more than you need, which is why I still hack out PERL scripts whenever I want to churn through a file for some quick one off analysis.

I know there are large projects written completely in dynamic languages though, have you written one, and are there things you do to keep them maintainable?  I know you can create a rats nest with JAVA too, but at least I always know simple things like what variables I have access to and if my refactorings changed every instance calling my function.

[shakilsiraj]

One more thing to worry about is cross browser compatibility with JSF.
At my work we have two large projects, one in GWT and the other in
JSF. With the JSF project we are forcing ie9+ to use 1e8 compatibility
mode as it is very complex to upgrade the JSF code we have to the new
JSF frameworks. With the GWT one, it took us 2 days to convert the
project (mainly GWT & GXT version upgrades, minor CSS fixes, etc.) to
support ie9.