I know the Google GWT manager, and unless he's playing his cards very close to his chest, GWT is not EOL'd inside of Google. Google did "re-open source" GWT a

I know the Google GWT manager, and unless he's playing his cards very close to his chest, GWT is not EOL'd inside of Google. Google did "re-open source" GWT a few years ago, and unfortunately it coincided their (AFAIK unrelated) closing of their Atlanta office (where most of the old GWT team worked). So, it gave the impression of washing their hands of it, but in reality they a) staffed their GWT team back up to 4-5 people, and b) the open source model is much healthier for the project anyway. (Previously the master GWT SCM has literally Google's internal Perforce/etc. repository, so any patches from external contributors had to be fostered by a Googler that cared about your issue, which made it really hard/impossible to have an external community of committers.)