J2CL is the next-generation Java-to-JavaScript compiler that is currently being developed by Google. The GWT committee will decide if J2CL will be used for GWT 3 (or whatever the next major release of GWT will be called).
On Monday, May 9, 2016 at 3:53:16 PM UTC-4, steve Zara wrote: > > I misunderstood. I assumed that GWT and J2CL were basically the same > thing (or that GWT would be renamed J2CL! > > On Monday, 9 May 2016 17:30:45 UTC+1, Michael Zhou wrote: >> >> Google is definitely interested in Java 8 emulation, but most efforts are >> being spent on J2CL, which goes from Java 8 -> Closure-style ES6. >> >> On Sunday, May 8, 2016 at 4:53:17 PM UTC-4, steve Zara wrote: >>> >>> Thank you - it does highlight where help can be given. I'm really >>> surprised at the situation with Java 8 emulation - is this something that >>> Google is just not interested in? It seems odd given their description of >>> Java technologies that give them cross-platform development: Android JDK, >>> GWT, and j2objc, especially now that Google are soon to provide Java 8 >>> support for Android. Ah well. >>> >>> On Sunday, 8 May 2016, Jens <[email protected]> wrote: >>> >>>> Is there anything that can be done to assist with progress? Is there a >>>>> problem with lack of interest in GWT from, say, Google? Does GWT 2.8 >>>>> involve too many features when compared to 2.7? Is there a lack of >>>>> developers working on GWT? Are more testers needed? >>>> >>>> >>>> Basically it has been decided to ship Java 8 API support with GWT 2.8 >>>> and to make sure it works with the next Guava release which will require >>>> Java 8 APIs. If we don't do this then next Guava release would need to >>>> drop >>>> GWT support, which is bad. >>>> >>>> Currently some dependencies of stream support are in the review >>>> process, and stream support itself has already been implemented but not >>>> yet >>>> pushed to review. Also it seems like we need to fix some compatibility >>>> issues of our emulation with future Guava. >>>> Google developers do not work on Java 8 API emulation so GWT relies on >>>> contributions. Three people (including me) have worked on it in the past >>>> but of course we only do it in our spare time. >>>> >>>> You can also read some comments here: >>>> https://plus.google.com/104553077953666769660/posts/fb5HehBxHdC >>>> >>>> You can help review Java 8 related contributions on Gerrit as most >>>> "easy" Java 8 emulations have already been covered. What nobody has >>>> touched >>>> yet is java.util.Base64 (pretty easy though), CompletableFuture >>>> (discussable but we think its useful and can be emulated using native >>>> Promises or a fallback impl) and of course java.time (generally doable but >>>> a bit more work). >>>> >>>> -- J. >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "GWT Users" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/google-web-toolkit/4ISY79wAq04/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To post to this group, send email to >>>> [email protected]. >>>> Visit this group at https://groups.google.com/group/google-web-toolkit. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
