Most of your links refer to optimizations for writing pure javascript code.
GWT actually takes care of many of these issues out of the box . For
example ClientBundle helps to avoid too many HTTP requests and include CSS
optimizations.
That doesn't mean that it is impossible to write slow GWT app
I would like to add some more references here within the context of Memory
management.
--
http://www.draconianoverlord.com/2010/11/23/gwt-handlers.html
To avoid application-level memory leaks, when adding event handlers, you
need to think about:
What is the scope of the
Does anyone know of a list of best practices for handling
Performance/Memory/etc while using Activities, Widgets, UiBinder,
ClickHandlers, etc.?
Such as:
- Making sure widgets/components are GC'ed
- Patterns for reusing widgets/components instead of rebuilding
- Widgets to avoid or lean toward
