> > A bit off topic, but: The real value of GWT for me has been the ability > to write browser apps without HTML, CSS, JavaScript, and Java (you know, > spaghetti) - being able to use Java only. As you start adding HTML and CSS > to GWT apps (the UI part), I question the whole value of GWT. >
The value of GWT is its tooling support because it can reuse tooling from the Java world. That is literally the only reason that really counts. GWT is a leaky abstraction and will always be. If you refuse to learn more about the platform you are programming apps for (the web and its technologies) then you are limiting yourself. Good luck writing a smooth mobile website/app with custom UI and corporate identity theme without knowing HTML/CSS and browser reflows. But yes that is off topic. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
