>>I also understand, that no one likes such changes, but nobody is forcing
anyone to upgrade. He and his team can use his setup for the next 20 years,
if he wants to.
We always try to upgrade to latest stable version of any technology we use.
GWT 2.9.0 then J2CL etc.
If something is broken or
Hi all!
I am catching up on some statements in the last mails.
> First, let me say that I both understand and sympathize for the cases Elias
> describes: when you have sufficiently large team and/or project, even small
> changes in workflow could be extremely painful.
> No one likes that and I
Thanks Gordan Krešić,
Here is my "two cents".
I am in favor of J2CL adoption and I don't want to see GWT sharing COBOL's
fate either.
Yet, I hadn't realized that GWT has been under such a severe shortage of
maintainers.
But, I am wondering, what should we be considering as deprecated?
Java7
On 11. 04. 2021. 17:15, Jens wrote:
Generally this would be a decision made by GWT steering group but I have no
idea if this group still exists. So I am asking here for a decision how to
move on.
Although I contributed a thing or two for GWT, I wouldn't call myself a
contributor (I'm not
> You can start servlets and CodeServer with one click.
Indeed, but don't ignore that this requires more setup work, which is not
making the overall process simpler.
It is extra steps which we are unhappy to embrace.
> Compiling the GWT client code happens automatically on refreshing the
