The risk of using a technology that is abandoned after some time is always a factor. But GWT is backed by a company that is using it for many important public applications so I would not worry too much.
I think you run way more risk by using jquery and all its contributed extensions (just to give one example). Worst of all: you can write everything yourself ... but are you capable of supporting all browser version into the future with little time investment ? I don't think so. David On Fri, Aug 7, 2009 at 3:48 PM, transient<[email protected]> wrote: > > Hi everybody, > > I've always feared technologies that work the way GWT does, because if > GWT stops being updated everything built on it will stop working if > users keep updating their browsers. I mean, if I develop an > application with GWT 1.7, which supports FF3.5 for instance and then > GWT stops being developed and FF4 comes out and some of the features > are broken there's nothing I can do to solve it except going native on > that feature. > > What do you think of this? What makes you not fear this? I know having > Google behind should be a pretty good guarantee but who knows... > Obviously this concern has no meaning if your customer asks you to > develop an application up to a specific browser version, this way > you're only responsible to support this version, but what if you're > developing for the web, which users you can't control, do you trust > GWT? > > Thank you for your opinion! > > Best regards > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
