>>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 gets discontinued we get locked to an older 
version.
So, indeed nobody is forcing anyone to upgrade but not upgrading is not a 
good option either.
e.g. if DevMode with embedded Jetty gets removed we are stuck with current 
GWT version, not good.

>>I am very thankful for all the work which was put into GWT.

Great work indeed.

> If we are to save GWT, not only we should drop ALL deprecated stuff ASAP

We could remove Java 7 support perhaps.

On Monday, 19 April 2021 at 11:52:05 UTC+1 bernhar...@schubec.com wrote:

> 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 can understand why not only Elias but probably 
> many other may feel reluctant (to be polite) about any 
> non-backward-compatible changes. 
>
> 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. 
>
> > I really don't see how investing into tech that has been deprecated for 
> years could benefit project in general. 
>
> 100% agree! 
>
>
> > If we are to save GWT, not only we should drop ALL deprecated stuff ASAP 
>
> 100% agree! 
>
>
> I have the feeling, that a small minority is blocking all the innovations 
> (by not allowing do drop deprecated stuff) and make life hard for GWT 
> maintainers and thus blocking us all from more/faster innovations. 
> I would suggest just not listening to them. 
>
> I am very thankful for all the work which was but into GWT. 
> I can use it free-of-charge. 
> Unfortunately, I am not good enough as a coder to become a maintainer, but 
> I did and will donate to various GWT / GWT related projects and I can say 
> „thank you“ and support their journey to have a maintainable GWT stack 
> without old stuff. 
>
> If there are big enterprises with big GWT projects, they sure have the 
> money to either upgrade the software and train their stuff to a recent GWT 
> setup or to hire someone who backports stuff for them if really necessary. 
>
> Thanks 
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/cb114439-2b29-485b-bca1-c756df176f69n%40googlegroups.com.

Reply via email to