On 4/1/12 12:39 AM, Asa Dotzler wrote:
> Is there anything obvious we can do to trim things back down some?
Trade off performance for space and turn off quickstubs and new DOM
bindings.
Rip out support for a few media or font formats.
Change compiler optimization options to focus on size, not speed.
Take out the OpenType sanitizer or the GL sanitizer.
In general, find features which involve too much code and get rid of them...
An actual binary diff showing which symbols have added size would be
needed to say more precisely what those are. We used to run that test
on Tinderbox, but stopped, since it mostly showed us adding features...
> Has it been a steady growth or did it recently spike up?
The former.
> Is this current size acceptable?
By what metric? It's a smaller size than our competitors, last I
checked. There's a limit to how small we can make compiler output
without trading off on performance, in general.
> Is Gecko that much bigger or is it Firefox front-end?
Gecko is a lot bigger, for sure. Whether it accounts for the whole
increase, I don't know.
> Also, our Mac download is over 39MB :\
It also includes two complete copies of Gecko (one 32-bit, one 64-bit),
right?
-Boris