I have the same concerns as the last comment. We are a java shop and use
enterprise java for our back-end. We have been using GWT for the last 9
years to write thin front ends for our applications. Basically GWT RPC and
UiBinder are 99% of the code we deploy. If I need to replace those with
I'm excited that you guys are planning a radical change (really). I hope it
becomes more clear on what we should be using to future proof our apps.
I hope we will get some usable preview of Singular (if that is really going
to be a replacement).
Somehow I am not totally concerned that we will
Hi,
I'm also frustrated about which technologies to use on new GWT projects
(see
https://groups.google.com/forum/?fromgroups#!topic/google-web-toolkit/_QSayBAmeX8).
But when it comes about the name, GWT should stay. The basic idea around
GWT is writing code in Java which is then recompile (or
Also think of people who use GWT for non web based project.
We use GWT for example to create native mobile apps with Titanium. And our
customers love the UI Binder support.
Dropping UI Binder means we wont be able to support new version of GWT.
Such a bad move.
On 14 June 2015 at 16:22,
Hi all,
thanks for sharing your views in this discussion.
Let me add a little background:
Currently we the GWT team have decided to work on a new fast transpiler
from Java to Closure (our internal enhanced version of JavaScript). This
makes sense for a lot of reasons that I won't go into detail
