I agree with what James wrote. There is a whole class of alt-js languages
that compile to javascript. GWT if by far the most mature and usable. You
can use the mature widget library for Enterprise kinds of stuff, our use
low level browser api's and Elemental to write 'to the metal' browser
Hey emurmur, I'm actually about a week or two away from releasing a fork of
the collide project (a collaborative web IDE built by Google, but abandoned
when they closed Atlanta). It has an integrated gwt compiler that runs in
the server, and super-dev-mode recompiles it's own running source
GWT is still alive and well. 2.5.1 is getting released soon, and work is
happening on 2.6 already.
The main reason why there is less attention being paid to GWT is that it is
a mature library; there's still lots of work and maintenance to do,
but as for the core features, it's all there
With recent things like the development of Dart and the moving of GWT to a
steering committee, I'm a little uncertain about GWT's future. To those of
you more experienced with it - does it still make sense to use for new
projects?
--
You received this message because you are subscribed to the
There has been quite some talk about that especially after the release of
GWT 2.5 and the transition to a steering committee.
Check the following posts:
The Future of GWT Report
2012https://vaadin.com/blog/-/blogs/the-future-of-gwt-report-2012
The History and Future of Google Web
Thanks, I'll take a look at those.
On Fri, Feb 22, 2013 at 8:31 PM, MAQ m4des...@gmail.com wrote:
There has been quite some talk about that especially after the release of
GWT 2.5 and the transition to a steering committee.
Check the following posts:
The Future of GWT Report
