Because all these non native JsTypes are considered entry points to your 
application when they are exported and thus all code referenced by them can not 
be pruned and maybe some other optimization a can't be applied to it as well.

Now consider GWT libraries that use non native JsTypes to export their API to 
JavaScript so they can be used by an Angular UI or similar. If it would be the 
default then lots of apps would miss optimization opportunities just because 
they use the libraries and might not use any pure js at all.

This is especially harmful as the flag is an all or nothing flag. So you have 
to explicitly decide to export to JS. in the future you should also be able to 
define a regex which tells the compiler which classes to export. This will be 
helpful if you depend on multiple such libraries but your app only needs to 
export one if them as well.

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/e7654865-f07e-4b45-8b82-dd8ebbb0b113%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to