It's interesting that these recent posts from the FF top ranks don't address this bundling issue.
It seems as though the world is moving to an 'appliance' plus app-store model. In that world the browser is part of the appliance and considered part of the purchase by the consumer. In that world, the only way for FF to have a presence is via hardware partnerships.
Yet another FF alumni alludes to the threat in a comment on the 'Chrome won' post [1] (my emphasis)...
"...for historical reasons Web sites targeting large-screen non-touch devices tend to configure themselves in a more standards-friendly way. ChromeOS is changing that; it has the form factor of a desktop platform, but not the third-party browser viability. If Android expands into that space, or Windows and MacOS get locked down a lot more, then that also closes up the window for Firefox."
have the team come up with a list of achievable meaningful milestones (eg. 'eliminate use of nasty obsolete library X'), ensure some time is spared to progress them; it'll become clear if the team is net paying off or accruing
also, find someone who thrives on eliminating crap and let them get stuck in
It seems as though the world is moving to an 'appliance' plus app-store model. In that world the browser is part of the appliance and considered part of the purchase by the consumer. In that world, the only way for FF to have a presence is via hardware partnerships.
Yet another FF alumni alludes to the threat in a comment on the 'Chrome won' post [1] (my emphasis)...
"...for historical reasons Web sites targeting large-screen non-touch devices tend to configure themselves in a more standards-friendly way. ChromeOS is changing that; it has the form factor of a desktop platform, but not the third-party browser viability. If Android expands into that space, or Windows and MacOS get locked down a lot more, then that also closes up the window for Firefox."
[1] https://andreasgal.com/2017/05/25/chrome-won/