3 ms·

I'm not sure how to read the Go Faster docs [1]. I undestand that they can get updated silently, but it doesn't say anything about pushing new ones. I assume th

I'm not sure how to read the Go Faster docs [1]. I undestand that they can get updated silently, but it doesn't say anything about pushing new ones. I assume that's also possible, as it totally makes sense, but I don't have any proof. The Go Faster initiative seems to have started around June 2015 [2] with Pocket being one of the first users [3] [4]. > The Presentation addon IIRC handles some prompts Thanks for the information. [1] https://wiki.mozilla.org/Firefox/Go_Faster/When_To_Use_System_Add-ons https://wiki.mozilla.org/Firefox/Go_Faster/When_To_Use_Syste... [2] https://wiki.mozilla.org/Firefox/Go_Faster/Meetings https://wiki.mozilla.org/Firefox/Go_Faster/Meetings [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1215694 https://bugzilla.mozilla.org/show_bug.cgi?id=1215694 [4] This first comment in #1215694 has a nice Orwellian tinge: "We're moving pocket to a built-in addon. This will facilitate user choice [...]". We all know how that went.

Manishearth 9y ago
> but it doesn't say anything about pushing new ones. I assume that's also possible, as it totally makes sense, but I don't have any proof. I don't think they can be > with Pocket being one of the first users [3] [4]. So were Hello/Loop. I think you've got the cause-effect backwards here. It seems to have started off as a way to add experimental features that needed a different update cycle (before Test Pilot existed). Now that Test Pilot exists all of these addons are basically for core browser functionality (e.g. the dev tools may move to this model at some point). So right now it's just a way of shipping code with a different release cycle, and being used for things that would otherwise be baked into the browser itself. Anyway, this is super off topic.