Originally posted by John Todd:
Which made me wondering about GWT performance at least from the client's view point (when he is loading the page) ?
The file size can be offset by the fact that GWT output was designed for easy compression. With the addition of a compression filter on your server-container you can cut the file size to a sixth.
Beyond this, the compiler gets smarter each version, and can optimize the code for the smallest possible file.
The GWT dev team (which is more than just Google) is quick to track down and fix reported performance issues.
The only issues that I have really seen are mega-apps with thousands of lines of code. There are at least a few people working on huge apps like this.
If you haven't seen Gpokr.com,
you should take a look. It is a real-world GWT app, probably a few thousand lines of code. The code file is 220K (compressed it would be ~40K). Ryan, the guy that wrote that app said that the playing card images are a lot larger than the GWT compiled code.
Rob
http://roberthanson.blogspot.com Co-Author
GWT in Action
