GWT is not dead! It's simply suffering from PR misunderstanding. People
think that you have to use the old widget system to use GWT, but you don't.
Just use Elemento instead of widgets and REST calls instead of RPC.
Regardless of what happens with GWT 3, using GWT 2.8 is future proof since
it
Ain't dead for me! Using it every day quite a lot. I still think it's a
great option if you have tons of widgets, panels, tabs... I see GWT
basically as an easier to distribute Java Web Start-like plataform.
I'm sitcking with *RPC* because it maximizes client-server code reuse.
DTOs, Enums,
I love GWT 2.8 and I appreciate all the work that the community has put
into it as well as the work towards GWT 3.0. I'm trying to understand what
the advantage of GWT 3.0 is though. It seems like GWT 3.0 is a subset of
GWT 2.8 with a different compiler under the covers. How is the closure
This is my opinion (from a person with more than 30 years of experience in
software enginnering), and I respect every other persons opinion - I'll
just not put my eggs on this basket for another 8 years "just to see if it
will get better".
Last year I had big issue with dates, because GWT has
On Sunday, June 2, 2019 at 1:22:09 AM UTC+3, Edson Richter wrote:
>
> This is my opinion (from a person with more than 30 years of experience in
> software enginnering), and I respect every other persons opinion - I'll
> just not put my eggs on this basket for another 8 years "just to see if it
On Saturday, June 1, 2019 at 10:51:55 PM UTC+3, Andrew Buck wrote:
>
> GWT is not dead! It's simply suffering from PR misunderstanding. People
> think that you have to use the old widget system to use GWT, but you don't.
> Just use Elemento instead of widgets and REST calls instead of RPC.
>
On Sunday, June 2, 2019 at 1:19:40 AM UTC+3, Douglas de Oliveira Mendes
wrote:
>
> Ain't dead for me! Using it every day quite a lot. I still think it's a
> great option if you have tons of widgets, panels, tabs... I see GWT
> basically as an easier to distribute Java Web Start-like
