I agree fully with Paul's comments and I do have great respect for a number of the authors and have indeed heard them speak on a number of occasions however I do get the sense that there is an element of bias towards native javascript and, in my personal view, a lack of exposure to GWT..
I've been using GWT for a over 6 months now and have written a quite complex application that works very well and a great deal of that is to do with the GWT technologies- I'm not suggesting that it could not have been achieved with native javascript but that (for me) would have been much greater of a challenge than starting with GWT and I personally have not run into the negative points that the authors have raised.. Giving what I know now (after being exposed to GWT "*in anger"*) - I would still continue to utilise the GWT technology on future projects as I don't believe by using javascript would give me any advantages but I do believe that it would give me a number of disadvantages (across the complete development lifecycle). Regards, Ian. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/hEssPJygyZgJ. 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/google-web-toolkit?hl=en.
