On Wed, 01 Aug 2012 22:43:30 +0200, Casper Bang <[email protected]>
wrote:
I don't know Vaadin, but I would argue that this issue concerns the
official GWT development stack - which does indeed rely on the
development
mode and thus, a browser plugin
I am curious though, how can you hook into
components and do your own (the nice thing about GWT is that one can use
OO
for reusability and extensionability), without having to compile these?
You can't do everything with Vaadin that you do with GWT. Basically you
just use the pre-existing components, and if you want some extension you
fall back into the long compilation. But this still allows you to do many
things.
Back to the original point, a possible theory is that Google is tired of
Javascript, which wouldn't be a big surprise given their focus on Dart. So
they could be working to a replacement of GWT made with Dart that
overcomes the hassles of GWT development. In the meantime, people can
still use and develop with GWT since it's being handled by its community.
As a Vaadin developer I feel safe even in the long term, since if Dart is
succesfull I can foresee a new version of Vaadin using it and being
backward compatible. Just speculating, of course.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
You received this message because you are subscribed to the Google Groups "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.
