On Wed, 01 Aug 2012 23:00:35 +0200, Casper Bang <[email protected]>
wrote:
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.
Well, except that Google is just replacing one cross-compiler with
another
- no less JavaScript, Chrome with native Dart support is still very much
work in progress and it's unlikely that all browsers will gain native
Sure, we're talking of a perspective of a few years, not something that
happens next Fall.
support the first couple of years.
The difference is that Dart, if I correctly recall, is not cross-compiled
but cross-interpreted to JavaScript. This means no long, multiple
cross-compilation, right?
And for what concerns other browsers, let's not forget that in the
meantime Chrome's market share is more or less on par with Internet
Explorer and well above Firefox. In a while they could be #1 and in future
they could have the chance of launching some Dart killer application, so
competition could *have* to add support for it. Again, just speculating.
--
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.
