Wow, I am impressed how much attention such a simple and non-technical question got.
But then again, I am about to give my own opinion so why am I surprised :) Of course I am not happy with gwt itself, that would mean I am content with it the way it is, whereas there are so many improvements I can imagine ;) ( by the way, if you haven't already done so, please take time to participate in the gwt survey http://bit.ly/GWT2012) Having said that, I really do believe that choosing gwt was smart, because it has the potential to redefine what we believe a web application to be. I am pretty sure soon no one will be able to distinguish between web, mobile ,application and website. And Google will once again, just like for the web in the good ol' times, have a helping hand in this;) Realistically speaking, developing a gwt app RIGHT NOW is just about as messy as tinkering with js/HTML/CSS directly, where you trade having to deal with browser-specific bs for having to deal with gwt-specific quirks. This is of course my own opinion ,but it might be noteworthy, that I came as a Java Application developer to gwt and most of CSS /js issues still feel like black magic to me. But those are rather issues with my lack of knowledge ( scattered ,incomplete, outdated,contradictory or simply wrong documentation seems to be norm in web dev) than with gwt itself. Thanks for asking this question, if it isn't already it should be part of gwt survey ;) Oliver -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
