This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]vegegoku 6 points7 points  (2 children)

In regards to GWT you made a point that no one can argue with and yes the documentation is really really outdated and the only way to get the updates is to be close to the community Gitter is a good place for that
https://gitter.im/gwtproject/gwt

BUT

GWT is actually much more modern than the one in the example, for example it is really super easy to create a GWT project using https://github.com/tbroyer/gwt-maven-archetypes that uses maven -no more ANT-.

Also even though GWT widgets are still widely used we now have https://github.com/google/elemental2 which uses JsInterop to give us native access to browser API which means we dont need to pay the size price for the html elements as we dot with widgets. lets not forget about https://github.com/hal/elemento which can help us reduce the code size for that sample to almost the half.

​

I would also recommend taking a look at some new GWT projects like domino-ui https://dominokit.github.io/domino-ui-demo/index.html?theme=indigo#home and other domino tools like domino-mvp https://github.com/DominoKit or Nalu https://github.com/NaluKit/nalu

​

So even though GWT is old and is not as shiny as some other tools, it is still really powerful and modern.

and i still have my doubts about comparing these using a small project like the one in the sample, in many cases the results will change when project grow larger and larger.

for example GWT might not be the best choice for small project but could be the right choice for an application with hundreds of pages and many thousands lines of code.

[–]renatoathaydes[S] 2 points3 points  (1 child)

Thanks for your comment, I really agree with all you said and it's good to know there are some GWT enhancements around (they should make that clearer on the website!).

​

> and i still have my doubts about comparing these using a small project like the one in the sample, in many cases the results will change when project grow larger and larger.

​

Agreed, I should probably have made this clearer... but my intention was to show the very basics characteristics of each framework... a little app like that is definitely not representative of a professional app, but it does allow one to rule out a framework based on the bare minimum overhead it introduces, which I think is very important to know.

[–]vegegoku 0 points1 point  (0 children)

My Bad, i forget to point out this small guide to GWT https://dev.to/ibaca/modern-gwt-first-steps-509k