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.
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
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.
--
You received this message because you are subscribed to the Google Groups
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
--
You
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
-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
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
On
