Closed Bug 1629006 Opened 5 years ago Closed 5 years ago

please analyze an alternative strategy: Chromium-based Firefox

Categories

(Firefox :: General, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: marius.andreiana, Unassigned)

Details

I've read Mozilla believes that they can contribute a perspective on the market that is more user-centered by owning and building their own engine, not being beholden to corporate interests that are not necessarily in favor of user agency.

Reality check:

Before closing this as 'heresy', would you please kindly consider doing an internal, non-biased, pros/cons analysis of the two alternative strategies, current and Chromium-based? Where will Mozilla be in 1 year from now with each of them?

With a Chromium-based solution, Mozilla could focus development efforts on

  • privacy features
  • extensions store
  • other user-focused benefits (eg enable extensions in the mobile Chromium build).
  • developing additional web standard features, enabling developers to build more powerful webapps instead of Android/iOS native apps for some features (and go through Google&Apple approvals and revenue cut)
  • other privacy-oriented services, free and paid (eg email hosting, a Google Apps alternative...). Having just a web browser is no longer enough to keep users, as other services like Google Search, Google Apps, MS Windows prompt users to switch browsers.

I'd prefer to store my data with Firefox Sync instead of Google, while not wasting time on issues already solved in other browsers. For example, I tried to switch to Firefox 75 on Linux today. Chrome passwords import doesn't work on Linux, fonts are bad. Spent 1hr to tweak various font settings suggested by others, then gave up.

I also understand some Mozilla engineers prefer to stick to current code as that's their baby. The alternative means to give it up, but consider adopting & making other babies benefited by more people.

Please move this to some discussion forum or mailing list.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.