Quote (curaga @ Oct. 24 2007,18:53) |
1) the swiftfox way: drop pango support; some size decrease |
Quote |
2) with gtk1; more size decrease |
Quote |
3) with Xlib; most size decrease & most speed increase |
Quote |
4) when I compiled FF shared, instead of the 11mb half-static official binary, firefox-bin was 74k, loading times dropped, and the total dir size was ~400k smaller than the official.. |
Quote |
How much did loading times grow on a P1? Or is general browsing on low comps slower? The .jar's were packed without compression to archieve speed. If all Mozilla extensions were slowed down, how would that affect those without too much processing power? |
Code Sample |
libmozgnome.so libmyspell.so libnkgnomevfs.so libspellchecker.so |
Code Sample |
1. sstrip firefox-bin 2. upx --best firefox-bin 3. du -cs components/ firefox-bin 1648 components/ 4104 firefox-bin 5752 total 4. tar -zcf test.tar.gz components/ firefox-bin 5. du test.tar.gz 4548 test.tar.gz |
Code Sample |
1. sstrip firefox-bin 2. du -cs components/ firefox-bin 11628 components/ 68 firefox-bin 11696 total 3. tar -zcf test.tar.gz components/ firefox-bin 4. du test.tar.gz 4768 test.tar.gz |