I may be wrong, but I don't think modules have much to do with performance. The reason I say this: At compile time, your modules are all mashed together and made into one big source for the various JS outputs. Using runAsync would definitely have more of a performance benefit than splitting code into different modules.
Modules are more about organization. runAsync is about optimization/ performance. On Feb 23, 2:45 pm, bkbonner <[email protected]> wrote: > I just want to verify a bet I have with someone. > > A primary benefit of modules is reuse. Is there any benefit to > performance with using modules? > > It seems code-splitting with runAsync will have more of a performance > benefit. > > Help me settle this bet. > > The gambler. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
