Unless you write in the native language of your application container and remain fully versed in the variety and upgrades, you are in this same position regardless of your choice of library/compiler/ environment. If you write apps using Java and suddenly the complier stopped being compatible with some future version of Windows, you'd be forced with a rewrite. If you use JQuery as a javascript library, you are counting on them to remain current with browser variations.. It's really an age old problem that is best solved by looking at the company/organization behind it (Franks point) and other attributes (like open source, Tonys point).
My .02 USD..... On Aug 7, 10:16 am, Tony <fatd...@gmail.com> wrote: > Additionally, GWT is open-source, so if Google stopped supporting it > the community could continue to develop the code. > > On Aug 7, 11:13 am, Frank Stallone <toadwarr...@gmail.com> wrote: > > > > > I don't think that is a real concern given the direction Google's OS > > is going with apps seemingly being RIAs. > > > If GWT became unpopular then yeah that be an issue but I assume that > > means something better came along so why would you be using GWT?- Hide > > quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
