I think most people use GWT for internal/intranet applications where the browser deployment is known and can be controlled. This is in contract to wide spectred Internet sites primarily deemed for mass consumption where the model lives on the server. For the latter, people usually use Wicket, JSF, Stripes, Tapestry etc. These have the potential to do Ajax stuff too, but degrade nicer. Remember GWT is a RIA technology and must be judged in that context, and compared against Flex, JavaFX and Silverlight.
/Casper On 6 Jul., 23:23, Ido <[email protected]> wrote: > Hey Dick (and the rest), > > I'm not sure that GWT developers needs much more then: > "...GWT applications automatically support IE, Firefox, Mozilla, > Safari, and Opera with no browser detection..." > > It's true, that it would have been much better to get a look on it's > issues per browser version, for > example:http://www.quirksmode.org/compatibility.html > > But when you have a business case, you just want to be able to support > the main browsers (not in beta mode :) > BTW, we are using it in our internal tools and we are very (very) > happy with it. > > Hope it helps, > Ido --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
