On 15/10/13 17:06, Benjamin Smedberg wrote: > With the landing of bug 853301, we are now shipping ICU in desktop > Firefox builds. This costs us about 10% in both download and on-disk > footprint: see https://bugzilla.mozilla.org/show_bug.cgi?id=853301#c2. > After a discussion with Waldo, I'm going to post some details here about > how much this costs in terms of disk footprint, to discuss whether there > are things we can remove from this footprint, and whether the footprint > is actually worth the cost. This is particularly important because our > user research team has identified Firefox download weight as an > important factor affecting Firefox adoption and update rates in some > markets.
You have given on-disk footprint values, but surely download size values are the important ones for the issue you are raising? After all, some of this data may be very compressible, and some may not. > * currency tables - 1.9 MB > > These are primarily the localized name of each currency in each > language. This is used by the Intl.NumberFormat API to format > international currencies. > > * timezone tables - 1.7MB > > Primarily the name of every time zone in each language. This data is > necessary for implementing Intl.DateTimeFormat. I wonder if we could do this as a webservice? That is, when the browser is asked to render a timezone string or a currency string in a particular language, it goes and grabs all the data for that language. We could therefore have full support, but a one-off delay for each new language the user wanted to see UI rendered in (which, for most people, will be a very small set). We could ship a set of common ones plus the UI language one to reduce still further the number of times the service would get hit. Gerv _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
