Pocket makes Mozilla competitive on mobile because Firefox's market share on mobile is very low.
If you mean the server-side then fair enough, maybe this acquisition will help with that.
https://dxr.mozilla.org/mozilla-central/source/browser/exten...
It would be great to have access to article view to build other clients, such as a Linux client.
https://www.reddit.com/r/firefox/comments/5wio45/mozilla_acq...
[edit] also nnethercote is a Mozilla employee :)
Not me. I don't want a bloated Firefox; even if the bloat is well intentioned and fully open sourced.
Firefox is open-source and (fairly) easy to build - if you really want the utmost control then I'd suggest this is the best way to do it. You can easily do a build that has no Pocket integration.
There's a cost to the level of configuration that I assume you're advocating here. Not saying we can't get better here, but there's definitely an impact on code complexity, QA test combinations, and stability.
Having the codebase be as small as possible is a laudable goal - with browsers it is difficult since Web standards are fairly complex on their own, and being cross-platform brings along a lot of weirdness.
An important aspect of security is compartmentalization - for instance, using separate sandboxed processes for web content vs. the main UI (which runs with full user privileges).
Sandboxing is a good example here since it improves perf/stability/security but also adds to the size and complexity of the code.
Only in an abstract "we might have been able to implement security/performance improvements faster if we wouldn't have had to worry about breaking addons" sense. Any other effects are restricted to those people actually using the addon and don't affect everyone else.
A powerful extension interface can also be used to improve performance/stability: while e.g. adblocking certainly doesn't come for free, its cost should be more than offset by not running all that crappy code pulled from ad networks.
That's what extensions are for. Those who want it, can have it, those who don't, they won't. Everybody wins, no need to raise emotions.
Actually .. no. It was a very vocal minority.
In the past, I've written about [1][2] my views of Mozilla's audiences, and soon after, Mozilla's own internal audiences [3] were brought to my attention. Several of their 'user types' are either noted as averse to change or loss of control.
[1] https://news.ycombinator.com/item?id=13425956 [2] https://news.ycombinator.com/item?id=12192509#12194161 [3] https://blog.mozilla.org/ux/2013/08/firefox-user-types-in-no...
In a story that began two years ago with Pocket's integration by Mozilla [1] in Firefox [2], large segments of the userbase spoke out with scathing criticism.
This, at first blush, appears unrelated: Mozilla previously announced its Context Graph initiative, which was a bold undertaking to be built partially upon a new and emerging set of W3C standards to take back some of the control over linkage, metadata, and the consumption and annotation of web content [3] from big incumbent providers who run content portals, content silos, or content aggregators (largely the usual suspects, including Google, Facebook [4], Apple, Microsoft, and Yahoo [5]).
To understand this play, temporarily forget about Mozilla the Foundation, and think about Mozilla as a strategic competitor to the above. In the case of Pocket, a hard-to-deny side effect is that Pocket's presence in Firefox, despite the exact nature of the integration, is likely here to stay. While this is bound to frustrate many, Mozilla's competitors routinely ship software or entire platforms with tight captive integrations, against which competition has proven difficult to mount solely on the merits of values and philosophical purity.
[1] https://hn.algolia.com/?query=firefox%20pocket [2] https://hn.algolia.com/?query=mozilla%20pocket [3] https://news.ycombinator.com/item?id=13729525#13740110 [4] https://news.ycombinator.com/item?id=13375451#13375917 [5] https://news.ycombinator.com/item?id=12863565#12867493