I'm trying to understand my options. * Stick with 2.x and risk being left behind and the project becoming neglected due to split effort. * Try to migrate to 3.x and possibly throw away a big investment. * Look to move to something other than GWT.
Obviously we will also be taking action to isolate ourselves from this uncertainty. A lot of that is just good practice anyway. FWIW Our team works on a single app that is meant to have a life of 10+ years. On Monday, October 19, 2015 at 10:00:48 AM UTC+1, Jens wrote: > > Somehow people seem to forget that they don't have to migrate at all if > its not profitable. Just stay on GWT 2.8.x and only start new projects with > new technology. There will be plenty of companies that have huge apps that > will not be rewritten anytime soon (if at all) so IMHO GWT 2.8.x will > continuously get bug fixes for years. Maybe in the long run not from the > Google GWT team because Google has the power to actually migrate their apps > and will probably focus on the new compiler then once that has happened. > > Personally I consider the new Java to Closure compiler/transpiler as a > separate product. Migrating to a new product costs money and time so its > totally valid to not migrate. Our company will definitely not migrate > anytime soon unless there is an easy incremental migration path. Only new > stuff might be build with the new Java to Closure compiler. > > -- J. > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
