Of course generators and linkers should be maintained, especially if it allows user code to be made more Java 8 friendly. I am pretty sure quite some GWT users will have large applications that will stay on 2.8 as long as possible because its too costly to rewrite these apps. However they will likely use Java 8 sooner or later and Java 8 friendly APIs should be added to GWT 2.8.x over the time.
I think its an error to assume that the current GWT compiler / generators / linkers should never be touched again just because Google is working on J2CL behind closed doors. J2CL is a different product and honestly GWT 3 will also be a different product if its based around J2CL. So if Google engineers do not want to invest a huge amount of time in the GWT compiler anymore because they want to move all internal apps to J2CL in the long run then thats fine. However that should not prevent improvements to the current state of GWT. If I would be able to review the code of Colin I would do it but I do not have the knowledge of internal GWT compiler stuff. That actually brings me to my personal next point: It would be great to have an in-depth compiler documentation. -- J. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/94d40741-e31e-479e-9e16-e76879723560%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
