> I heard that it's shortlisted for end-of-life at Google because it's a hassle to work with.
Did you hear that from a Googler that actually knows their long term budget/support plans for GWT, or just the usual misguided rumors?
Right now Google has 4-5 full-time developers working on GWT because it's used by AdWords (huge) and literally 1,000+ other projects (private and public) inside of Google (including for parts the new "Sheets 2.0" of Google spreadsheets).
The end-of-life comment aside, which I'm admittedly defensive about, your other criticisms are unfortunately very valid.
Personally, I think a good framework is essential, and the compiler is a known issue that they currently have several smart people working on. We should see by mid-summer if they pull it off.
Did you hear that from a Googler that actually knows their long term budget/support plans for GWT, or just the usual misguided rumors?
Right now Google has 4-5 full-time developers working on GWT because it's used by AdWords (huge) and literally 1,000+ other projects (private and public) inside of Google (including for parts the new "Sheets 2.0" of Google spreadsheets).
The end-of-life comment aside, which I'm admittedly defensive about, your other criticisms are unfortunately very valid.
Personally, I think a good framework is essential, and the compiler is a known issue that they currently have several smart people working on. We should see by mid-summer if they pull it off.