|David Balme||Jul 30, 2008 9:12 am|
|Ian Bambury||Jul 30, 2008 3:53 pm|
|Ian Bambury||Jul 30, 2008 3:58 pm|
|Tim||Jul 30, 2008 6:21 pm|
|David Balme||Jul 30, 2008 7:30 pm|
|Ping||Jul 31, 2008 4:49 am|
|rusty||Jul 31, 2008 5:06 pm|
|Magno Machado||Aug 1, 2008 10:43 am|
|walden||Aug 1, 2008 12:24 pm|
|Magno Machado||Aug 1, 2008 12:35 pm|
|Ian Bambury||Aug 1, 2008 12:36 pm|
|Magno Machado||Aug 1, 2008 12:48 pm|
|Magno Machado||Aug 1, 2008 12:51 pm|
|Srini Marreddy||Aug 1, 2008 1:10 pm|
|Ian Bambury||Aug 1, 2008 1:11 pm|
|Maxim||Aug 1, 2008 2:30 pm|
|David Balme||Aug 2, 2008 1:13 pm|
|Arthur Kalmenson||Aug 4, 2008 8:02 pm|
|bru...@google.com||Aug 13, 2008 3:04 pm|
|Subject:||Google does not use its own GWT framework|
|From:||David Balme (davi...@gmail.com)|
|Date:||Jul 30, 2008 9:12:45 am|
Hello GWT developers:
I have been working with GWT for some time now. I'd say since about Nov 2008. I am very very impressed with your work.
I have to admit I did have concerns when deciding to formally adopt this framework within my organization for a couple of reasons. I'm a dev team lead and sometime dev-manager so I have to make responsible technology decisions.
(caveat - keep in mind that I refer to GWT 1.4 as I cannot put java 1.5 code into our prod environment yet)
So here were (and still are) my concerns:
.. But now my real concern... and my real motivation for writing this note..
3) As far as I can tell Google does not use GWT!!!! This is a problem of GWT credibility! Issues (1) and (2) are easily overcome through programming mechanics, training and creating GWT conventions and standards. However, a true test of any tool is that the creator of said tool actually uses the tool in a production setting. The sample applications, though good, are not enough to create this tool's credibility. Why is the rest of Google ignoring GWT? For example: As far as I can tell (by viewing page source) http://docs.google.com does not use GWT. This is a perfect Google GWT application candidate and would prove that Google is truly serious about GWT. I understand the realities of large organizations and different dev teams working in departmental sylos and not doing the requisite cross pollenation of ideas across different development initiatives. That happens everywhere. But if you GWT developers could convince your Google-docs counter-parts to use GWT then credibility would be established. But much more than that would occur. The google doc guys would end up being your clients and the GWT team would be forced to enhance the libraries as the Google-Doc team demanded more and more from you. Naturally the GWT code base would improve. So why not do it? Or have you done it already and I have not noticed?
Thanks very much for creating such a great Web 2.0 dev platform. I've stuck my neck out and picked your technology. I'd like to see that you guys have done the same and pick your own technology to write some of your own production applications.
Cheers and thanks for reading..
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group. To post to this group, send email to Goog...@googlegroups.com To unsubscribe from this group, send email to
Google-Web-Toolkit+unsu...@googlegroups.com For more options, visit this group at