> > There are are a lot of dependencies hanging off of > http://bugzil.la/fatfennec .. are there any low hanging fruit? > > Lots of things that will buy small wins, but most of the easy stuff has already been done.
Bug *1039898* <https://bugzilla.mozilla.org/show_bug.cgi?id=1039898> is rote. Free savings at the cost of churn. Bug *1044289 <https://bugzilla.mozilla.org/show_bug.cgi?id=1044289> *is just a matter of doing the work of reading the manifest, filing bugs and deleting lines. Bug 1044079 <https://bugzilla.mozilla.org/show_bug.cgi?id=1044079> mostly involves stepping on people's toes and turning shit off. Bug *1105546* <https://bugzilla.mozilla.org/show_bug.cgi?id=1105546> might be easy for some frontend folks. (Same with *1147960* <https://bugzilla.mozilla.org/show_bug.cgi?id=1147960> and *1130201* <https://bugzilla.mozilla.org/show_bug.cgi?id=1130201>.) Bug *1128675* <https://bugzilla.mozilla.org/show_bug.cgi?id=1128675> isn't exactly trivial, but should be an easy enough win. The rest typically require deeper build system or Gecko knowledge. At this point I'm mainly hoping for additional opportunities to add to the list, and a shift in attitude that will allow us to get traction on some of these. For example, I want us to reach the point where we can easily say: no, we're not shipping your 70KB chunk of JS just for desktop parity, or: please split up your big JS module into toolkit and browser so we don't have to ship all of it, or: we're turning off this C++ feature altogether because it's not a net win for our users. (There's a broader point here which is that we shouldn't assume that disk space at runtime is free, either, which means lazy-initing DBs etc. etc.)
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
