On Tuesday, July 3, 2012 9:32:51 PM UTC+2, C Anthony Risinger wrote: > > > i personally don't like the monolothic build at all, and IMO the > dynamic link should be the default. monolithic means that any change > -- even a single char -- *anywhere* in your app results in the client > downloading the full multi-MiB app in entirety. > > --dynamic-link allows only the changed modules to be re-downloaded, > while all others are cached. with some tricks, you can also achieve > cross-domain caching. > > i personally would use: > > --enable-strict --disable-debug --dynamic-link > > ... at the minimum. the first enables maximum python compat, the > second disables anything considered debug (even stuff enabled by > strict! this was the motivation for changes in option parsing), and > the third links modules by <script> tags instead of copying them into > the *cache.html files. > > i haven't tried the ompressor stuff yet, but the <script> loaded > modules are pure JS, and i think should be compressible as-is. > > I have enable the flags you mentioned ( --enable-strict --disable-debug --dynamic-link). As a result I have much smaller files, but more files (as expected). The application takes more or less the same time to download, but overall seems more responsive. I would say the total size has not changed much, but I like it better this way, so I would leave it active.
Thanks, Daniel
