Saturday, January 31, 2015

Re: Why doesn't GWT just export everything automattically

The reason I'm interested in this is because I've been in js interop hell lately. I'm trying to export my stuff to javaScript so that JavaScript code can use it. I'm having a lot of trouble though. Just exporting my regular stuff has been a lot of trouble. But exporting my libraries would involve a ridiculous amount of boiler plate code. I decided to just use javaScript for this part.

On Saturday, January 31, 2015 at 5:07:31 PM UTC-5, Joseph Gardi wrote:
Edit: the variables names in functions in javaScript code are shortened when minified but that's it. This doesn't cause issues because variables within functions don't need to be exported since they're limited to the scope of that function. Conversely, public variables and methods should be exported automatically. The minor performance loss should be ignored. Like Donald Knuth says: "Premature optimization is the root of all evil". 

On Saturday, January 31, 2015 at 4:58:15 PM UTC-5, Joseph Gardi wrote:
right now GWT will export things if you tell using GWT exporter. In the GWT 3.0 it'll you can use JsInterfaces etcetera which is much better than GWT exporter and built into the compiler. It seems like it'd still be very complicated to build a hybrid app with GWT and JavaScript because you have to tell the compiler what things to export. Why doesn't GWT just export everything automatically? This would be a dramatic simplification. I understand that there might be a small performance cost but I think it'd be worth it. Doesn't regular javaScript code remain accessible when minified? I don't see why GWT shouldn't do the same.

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment