> > 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 support the first couple of years. It makes a lot of sense for Google to abandon Java over Dart, and call me conservative, but I'm not not willing to bet in a community which swings left and right - I (or rather, the company I work for) require a minimum amount of standardization and official support, in order to guarantee their future livelihood. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/WBQy6b4KCj4J. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
