ongwt.com

It seems that the team is working on a multiple processes or machines GWT compiler : good news !

Massive refactor: enable multiprocess GWT compiles

1 comment

Scott Blum :

"Here are a lot of interesting things on the horizon for the Compiler that we have been talking about lately, more than we can probably do in Q1, in fact. I'm going to talk briefly about each of the major areas, the implications where it's non-obvious, and finally propose an order in which I think they should be tackled.
1) Java 5.0 Language support
2) Compiler Infrastructure
3) Some sweet optimizations
4) Metrics on generated code
5) Support dynamic module loading
6) Compiler support for JavaScript API "

Compiler enhancement possibilities for Q1

no comment

Memory leak issues like this is one of the many reasons we ended up building GWT in the first place. It's possible to characterize exactly which constructs do and do not cause leaks, but it's really tricky to maintain real code without causing them accidentally. And as you probably noticed, when you leak one object you tend to leak many of them because they all reference one-another.
JavaScript Memory Consumption

no comment