Hey Murray,
Pierre is right. GWT creates multiple permutations of your javascript
code ... 1 for each browser / locale combination. So if there are 10
locales (english, polish, french, etc) and 4 browsers (IE, Firefox,
Chrome, etc) it will create 40 different compiled JS files.
If you are only building your application for a single locale (ie
English) you can specify this to reduce your compile time. Here is
what I do in my application's module xml file:
<extend-property name='locale' values='en'/>
<set-property-fallback name='locale' value='en'/>
<set-property name='locale' value='en'/>
Also, as Pierre mentioned, using Hosted Mode is ESSENTIAL for gwt
developers. Hosted mode allows you to run your application without
compiling. You can even make changes which are immediately reflected
in your web application just be refreshing the page. Basically it is
using a gwt browser plugin to run java byte code in your browser.
Make sure you check out some of the Google IO 2009 presentations ...
they specifically talk about gwt's compile process, how it works, and
some tips to speed it up. But they definitely stress the importance of
Hosted Mode
I loved Netbeans, but eventually had to switch to Eclipse because it
has such tight integration with GWT and the ability to leverage the
Hosted Mode functionality.