I think you get it all correct; in particular J2CL != GWT3. J2CL is a separate/unbundled "Java to Closure style ES6" transpiler that Google works on and only shares the JRE emulation and JsInterop from GWT-SDK. There is an intention to open-source it when it is ready and J2CL+JsCompiler together 'may' replace the old compiler stack in GWT-SDK in GWT 3.0. That part is a decision that will be made by the open source community and steering committee.
On Fri, Nov 13, 2015 at 11:28 PM, Brian Pedersen <[email protected]> wrote: > I was at GWTcon, and my perception of Juliens keynote and his presentation > on JSInterop was, that he used AngularJS to demonstrate that it is now > possible to use a JS based framework with GWT 2.8 through JSInterop, and to > show solutions to common issues you might run into while doing so. > > Which framework you choose if you take this route, depends entirely on > your requirements and personal preference. It could be AngularJS or > something else, as long as it is javascript based. > > This approach should make our applications J2CL compatible. > > I also took the following note during the conference: 'J2CL != GWT3'. > > This again is my own personal perception. > > While the GWT team seems focused on doing the J2CL transpiler, and there > appear to be a clear expectation that the next major version of GWT will be > based on J2CL, the future of GWT seems unclear. > > /Brian > > > Den fredag den 13. november 2015 kl. 10.52.13 UTC+1 skrev stuckagain: >> >> This points to the GWTCon keynote done by Julien Dramaix. >> >> <https://drive.google.com/a/vaadin.com/file/d/0BwVGJUurq6uVa2tpaTRLSzlBMDQ/view?pli=1> >> <https://drive.google.com/a/vaadin.com/file/d/0BwVGJUurq6uVa2tpaTRLSzlBMDQ/view?pli=1> >> https://drive.google.com/a/vaadin.com/file/d/0BwVGJUurq6uVa2tpaTRLSzlBMDQ/view?pli=1 >> >> I was not able to attend the meeting but I wondered what was said about >> the last slide: >> Use modern framework instead of classic GWT libs >> >> In the same conference Julien also showed how you can use JsInterop to >> use AngularJS from GWT. >> This looked really nice, but does that mean that we need to start looking >> at AngularJS for any GUI work ? >> >> I'm just trying to get a clearer picture to decide what way to go for >> implementing a new application and I >> want to be as much future proof as possible. >> >> Should I use: >> - UiBinder >> - GQuery >> - AngularJS >> - Singular >> - GXT >> - Vaadin >> >> This application will have a extensive GUI and will need to be maintained >> for at least 10 years. Rewriting large parts is not something we want to do >> too often if not needed. >> >> -- > 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/54a3ffe7-6766-4741-8f8c-9f945c46d305%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/54a3ffe7-6766-4741-8f8c-9f945c46d305%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAN%3DyUA2AnWkAUdeYH%3DS_%2BLqYF%3DwzUtNkrj9FN1ENvB3-NDBvbg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
