One thing for sure is that the code base is still being actively developed if you look at the activity on the repository. It will be curious to see how much talk there will be about GWT at this years Google IO.
On Wed, Apr 18, 2012 at 10:50 AM, b0b <[email protected]> wrote: > The biggest problem with web frameworks is that you have no visiblity into > their future. > And the fact that sometimes Google does not hesisate to can products > doesn't help. > > The is very must unlike say J2EE which existed 10 years ago and that you > can mostly be guaranteed will still exist in 10 years because > so much production critical code use it in the industry. > > Being open source helps a bit, but there's many Open Source projects that > just die because noone work on it. > And we all know that code that isn't regularly > maintained/modernized/updated just dies and become irrelevant. > > Athough I do not think GWT risk being abandonned soon, who knows in which > state it will eb in 2 or 3 years ? > > > > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/mXcfTwGGCc4J. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
