I am also quite deceived by the fake-arguments from M. Fowler... As a user of
GWT since 1.6, i can say that i would not have acheived all the applications i
wrote by writing pure Javascript. Neither would i be able to write big native
applications by writing pure assembler (even macros would
My comments to ThoughtWorks radar (I guess they are not from Martin Fowler,
but from some more novice JS developer):
write Swing-like Java code...
GWT widgets are much simpler and cleaner than Swing. But you don't have to
use GWT widgets - you can use UI Binder with pure HTML and style it with
Generally I agree with most of the comments,
GWT is trying to bring sanity (which is good) to an insane platform
HTML/CSS/JS essentially a document viewing platform gone mad.
However
1) GWT widgets are not simpler than Swing. I have done Qt (that's sane),
Swing (so and so with occasional
Bunk and bunk. It reminds me of when some Javascript Engineer consultants
sent out an email crapping all over GWT several years ago at a major global
bank I worked for that used GWT as their standard UI toolkit. They cited a
whole bushel of straw man and red herring arguments while only
+Joseph Lust.
Amen !
They simply dont get the awesomeness of GWT.
2014-08-11 18:22 GMT+02:00 Joseph Lust lifeofl...@gmail.com:
Bunk and bunk. It reminds me of when some Javascript Engineer
consultants sent out an email crapping all over GWT several years ago at a
major global bank I worked
I'm definitely not blind to GWT's shortcomings and I'm also worried about
its future. BUT I can't see anything that seems more attractive to me.
I really like JavaScript for bits and pieces but my tired old brain is
helped by Java, strong typing, IDE help...
Also the quality and depth of the
I to have been following this disucussion for some years now. Google is
still developing gwt and using in in main products. In my opinion the gwt
community is growing. But these old articels keep popping up. They are old.
Jboss is developing Errai. A framework on top for gwt. so are vaddin and
IMHO GWT has two huge selling points:
- Compiler
- Java
The compiler does a really good job in producing optimized code (both code
size as well as speed).
Javascript VMs do a lot of optimizations nowadays but they require that the
developer doesn't throw it off the hot path. Here a
That was true of GWT 1.x, much less of 2.x but was still how most people
approached (and still approach) GWT. But the web is changing and GWT adapts to
the changes. I've been told Google uses almost no widget. In Spreadsheets 2
they use Closure Library for the UI and GWT for the portable code:
Hi,
I am asking about the future of GWT (here, in France, it does not seem
that is have a so good reputation, but this is just my feeling)
*I have read this article : http://www.thoughtworks.com/radar/platforms/gwt
(the citation is at the end of this mail)*
*Martin Fowler, a worldwide
Thoughtworks is trying to sell a product, and the concept of their products do
not match GWT. So they are therefore going to be against it.
Also, you should never preselect a tool to match the requirements. One major
requirement often over looked is the ongoing MX costs, therefore you should
I was forced to use GWT back in january this year (as a consultant you
often do have to use a specific tool just because) and it's been somewhat
of a bumpy ride; at first I hated it with a passion, then I started to
appreciate the strengths it does provide.
Losing devmode was/is a huge blow,
12 matches
Mail list logo
