5 ms·

None of the class names used are GWT class names, so I doubt it. It'll be the output of an internal template engine. Interestingly, AFAIK, most of Google is not

None of the class names used are GWT class names, so I doubt it. It'll be the output of an internal template engine. Interestingly, AFAIK, most of Google is not written in GWT -- anyone know any production Google stuff that is? (I think Wave is.)

mcxx 16y ago
GMail is.
- litewulf 16y ago
  Gmail is not.
- csytan 16y ago
  I believe you are mistaken. Gmail came out much earlier than GWT.
- Robin_Message 16y ago
  I'm pretty sure that it is not GWT since: 1. It was released several years before GWT. 2. It has no GWT CSS class names on anything. 3. It does have some weird IFRAME structures that are unlike what GWT uses. 4. It doesn't have any of the long hexadecimal identifier files that GWT uses to compile to different targets. 5. On the wire, it doesn't look at all like GWT AJAX requests. 6. Isaac Truett <itru...@gmail.com> says it isn't at http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/beb685af839718d2/2dd5665b53a6eb11 http://groups.google.com/group/Google-Web-Toolkit/browse_thr... This was in 2007, but I don't believe they threw away a working product to do a rewrite in GWT, which was still not fully mature and is still hard to get just right. And if they did, they'd also have had to make it look like it is not written in that framework in every way I can think to check easily. (EDIT) 7. Since nothing significant is written in GWT, they'd be trumpeting it from the rooftops if GMail was.
- falien 16y ago
  "Currently, the Gmail program is comprised of 443,000 lines of JavaScript, with 978,000 lines if comments are included. All of it was written by hand, he said." http://www.computerworld.com/s/article/9178558/Google_to_use_HTML5_in_Gmail?taxonomyId=11&pageNumber=2 http://www.computerworld.com/s/article/9178558/Google_to_use... edit: "currently" with that article being published June 25, 2010
mason55 16y ago
The ads stuff is done in GWT (meaning managing campaigns, stuff like that). Gmail definitely is not GWT.
- deleted 16y ago
  [deleted]
eneveu 16y ago
Wave is indeed developed in GWT, and the Adwords management interface was rewritten in GWT in the recent years (as mason55 mentioned). They talked a lot about it during Google I/O 2009 (the session videos are still available online: http://code.google.com/intl/fr/events/io/2009/sessions.html#gwt http://code.google.com/intl/fr/events/io/2009/sessions.html#... ). While not a "web app", SpeedTracer ( http://code.google.com/intl/fr/webtoolkit/speedtracer/ http://code.google.com/intl/fr/webtoolkit/speedtracer/ ) was also made using GWT. What's interesting, is that with the Adwords UI, Google started using GWT on an enterprise app, and thought about ways of writing such an app. This project lead them to introduce many best practices for large GWT enterprise apps: - MVP (Model View Presenter) and testable UIs: MVP is good for SoC, but it's also very important if you want to unit test your UI logic in pure java (which is a lot faster than GWTTestCases) - EventBus - Command Pattern - UIBinder (declarative UI in XML) Ray Ryan's talk ( http://code.google.com/intl/fr/events/io/2009/sessions/GoogleWebToolkitBestPractices.html http://code.google.com/intl/fr/events/io/2009/sessions/Googl... ) at Google I/O 2009 created a lot of interest around these concepts, and many GWT developers around the world started discussing / following them. Google I/O 2010's sessions also have a lot of talks about these subjects, and while the best way of writing GWT apps is not yet known, we are getting there.

mcxx 16y ago

GMail is.

litewulf 16y ago
Gmail is not.
csytan 16y ago
I believe you are mistaken. Gmail came out much earlier than GWT.
Robin_Message 16y ago
I'm pretty sure that it is not GWT since: 1. It was released several years before GWT. 2. It has no GWT CSS class names on anything. 3. It does have some weird IFRAME structures that are unlike what GWT uses. 4. It doesn't have any of the long hexadecimal identifier files that GWT uses to compile to different targets. 5. On the wire, it doesn't look at all like GWT AJAX requests. 6. Isaac Truett <itru...@gmail.com> says it isn't at http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/beb685af839718d2/2dd5665b53a6eb11 http://groups.google.com/group/Google-Web-Toolkit/browse_thr... This was in 2007, but I don't believe they threw away a working product to do a rewrite in GWT, which was still not fully mature and is still hard to get just right. And if they did, they'd also have had to make it look like it is not written in that framework in every way I can think to check easily. (EDIT) 7. Since nothing significant is written in GWT, they'd be trumpeting it from the rooftops if GMail was.
falien 16y ago
"Currently, the Gmail program is comprised of 443,000 lines of JavaScript, with 978,000 lines if comments are included. All of it was written by hand, he said." http://www.computerworld.com/s/article/9178558/Google_to_use_HTML5_in_Gmail?taxonomyId=11&pageNumber=2 http://www.computerworld.com/s/article/9178558/Google_to_use... edit: "currently" with that article being published June 25, 2010

mason55 16y ago

The ads stuff is done in GWT (meaning managing campaigns, stuff like that). Gmail definitely is not GWT.

deleted 16y ago
[deleted]

eneveu 16y ago

Wave is indeed developed in GWT, and the Adwords management interface was rewritten in GWT in the recent years (as mason55 mentioned). They talked a lot about it during Google I/O 2009 (the session videos are still available online: http://code.google.com/intl/fr/events/io/2009/sessions.html#gwt http://code.google.com/intl/fr/events/io/2009/sessions.html#... ). While not a "web app", SpeedTracer ( http://code.google.com/intl/fr/webtoolkit/speedtracer/ http://code.google.com/intl/fr/webtoolkit/speedtracer/ ) was also made using GWT. What's interesting, is that with the Adwords UI, Google started using GWT on an enterprise app, and thought about ways of writing such an app. This project lead them to introduce many best practices for large GWT enterprise apps: - MVP (Model View Presenter) and testable UIs: MVP is good for SoC, but it's also very important if you want to unit test your UI logic in pure java (which is a lot faster than GWTTestCases) - EventBus - Command Pattern - UIBinder (declarative UI in XML) Ray Ryan's talk ( http://code.google.com/intl/fr/events/io/2009/sessions/GoogleWebToolkitBestPractices.html http://code.google.com/intl/fr/events/io/2009/sessions/Googl... ) at Google I/O 2009 created a lot of interest around these concepts, and many GWT developers around the world started discussing / following them. Google I/O 2010's sessions also have a lot of talks about these subjects, and while the best way of writing GWT apps is not yet known, we are getting there.