Sounds like I'm late to party; I missed the 2015 meetup videos, does someone have a link? (That will teach me to not login to G+ very often...well played, Google...)
Not that my opinion matters very much (vs. the GWT team who's doing all the actual work), but I'll +100 any plans for large/breaking changes/rewrite for GWT 3.0/j2cl. Everyone that is concerned about backwards compatibility, you can stay on GWT 2.x. What we need is foundations for a GWT that will be awesome 5 years from now. For the next generation of applications. That's who we need to be worried about. Yes, that means pain/being left out for the current generation of applications, but that's how technology works. GWT 2.x will not suddenly be taken off Maven central. Plenty of enterprise applications rely on older/mature technology, e.g. jars/projects that aren't pushing out new releases every 2 months with amazing new features. That's fine. If it's too expensive to switch, then don't. Sounds like a great opportunity for other companies to step-in and provide enterprise support for 2.x as well. Google has never been interested in that game anyway. Someone mentioned early access to j2cl for framework authors to start porting; I'd throw my hat into that ring. It would be interesting to see what Tessell looks like with it. Tessell very heavily uses UiBinder to drive its MVP codegen, so I'll have to either port Tessell to the next-generation of templates, or (more likely) port UiBinder to j2cl (using APT/something; maybe not 100% backwards compatible, but at least something that is not "throw away all your templates and start from scratch"). - Stephen On Saturday, June 13, 2015 at 4:03:08 AM UTC-5, Paul Robinson wrote: > > The GWT Meetup 2015 videos are very interesting. > > > I can see why the proposals for GWT 3.0 have been made. However, we should > be clear about the fact that GWT 3.0 is not just going to break a few > little things that can easily be fixed, but break things to the point that > it's a completely different product and there will be lots of GWT > applications that will never be ported to the new system. > > > It will be confusing to all GWT users to continue to use the name GWT 3.0. > It would be much better to use a new name for the new system and treat it > as what it is: a new idea about how Java can be used to build modern web > applications. > > > The situation we have now is that GWT will end at 2.8 and a new thing, > that is currently vapourware, will be coming that people are expected to > use. There's going to be a lot of confusion and those using GWT now, as > well as those that will use the new thing when it does exist, will all be > served much better if everybody stops calling the new thing "GWT". > > > Paul > > > -- 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/afebe594-679a-4ff6-b270-3cb0861986fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
