Bump
I'm really curious if anyone can help me understand how code splitting
can be useful given the experience I have had with it. It really makes
little sense why the overhead is so huge.
On Feb 5, 4:16 pm, Sky myonceinalifet...@gmail.com wrote:
Sorry, I have to retract that last post
I have an application whose 600k+ size dropped to about 100k for the
initial download using code splitting. Not every app will benefit
from code splitting, it really depends on how modular your app is -
are there big pieces of functionality that stand alone, or is
everything woven together?
I
I successfully used code splitting on a few classes in my project. By
looking at the compilation report it appears to me that code splitting
has an incredibly large amount of overhead.
I've gone through the report carefully and the code that I'm splitting
is indeed being split and not included in
It appears I am wrong.
If you notice this, don't bother reading my entire blurb above,
instead learn from what I will explain here that was my mistake.
I put inside my onFailure() method a call to the method that calls
GWT.runAsync() and creates the async handler, effectively making it
retry to
Sorry, I have to retract that last post entirely! I made a mistake in
testing it when I removed that one line of code. I forgot that I was
no longer actually calling GWT.runAsync() and thus it had gone back to
it's original Initial download size. Even removing the retry code,
but properly using
