> easily cross 1.5 MB I don't agree with "easily". A few things: - Perform efficient coding. - Use Soyc to optimize your code splitting. - Transferring the files gzipped between browser and server will deliver a file reduction of about 50%.. - Using multiple modules if size is getting too big. - etc..
Result: It's hard too cross an 1.0 MB initial load. On Wed, Dec 21, 2011 at 6:14 AM, -sowdri- <[email protected]> wrote: > If speed is critical for your application then there are 2 things to > consider: > > 1. Speed after the application is loaded. > 2. Speed in which the application loads up. > > If you are concerned about latter, then you have to either use code > splitting or consider moving to jsp. Because in a large application the > code size could easily cross 1.5 MB which might take a long time to load. > > If the former is of importance(which actually makes the app interactive) > then GWT is definitely the way to go. > > -sowdri- > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/XrqHJ8falFQJ. > 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. > -- 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.
