I've been meaning to write almost exactly this blog post for a while now, glad that someone else did it.
Two things that I think are worth calling out:
1. In many ways Apple's anti-competitive behaviour on iOS/iPadOS is a blessing. It's one of the few things that keep Chromium's dominance in check. Of course, it's not great that Apple are stifling innovation like this, but consider the alternative: Chromium dominance on all platforms.
2. Why it's worth caring about this at all? So what if Chromium is the only engine, it would make things easier for developers after all. To this I say, go read some of the discussions in standard bodies(for example about FLoC). Engineers from Apple and Mozilla are largely our bastion against Google's harmful proposals for the web. Pushback from Apple and Mozilla are only relevant as long as they have market share to speak of. The recent lawsuit against Google(summary[0]) by many US states should be extremely worrying to anyone that cares about the open web and it should make handing over any more control to Google a terrifying prospect.
Mozilla maintains a list[1] of their positions on various standard suggestions that is also a useful resource.
> 1. In many ways Apple's anti-competitive behaviour on iOS/iPadOS is a blessing. It's one of the few things that keep Chromium's dominance in check. Of course, it's not great that Apple are stifling innovation like this, but consider the alternative: Chromium dominance on all platforms.
I think it’s worth noting that (at least I believe) the reason apple limit the usage of other browser engines in iOS isn’t (mostly) about maintaining control and dominance. It’s about battery usage, WebKit is heavily optimised on iOS to ensure optimal power efficiency. The number one priority is that the lowest denominator of iPhone user is happy with their device, and battery usage is the number one KPI people care about.
I don't disagree that is their publicly stated reason for the limitation. Them having the ulterior motive of stifling PWAs on iOS and competition for mobile Safari is a common theory.
Whether they do have ulterior motives or not, the effect is that innovation is stifled.
Remember that Apple doesn't allow other web browser engines in any application. Imagine if an Electron application on iOS just decided to ship with it's entire, own browser engine. We would have super-bloated apps like our desktops, and if a security flaw was found, good luck getting all those apps to update.
In a way, Apple knows that allowing other browser engines means:
1. Chromium-based browsers just increase their monopoly, Firefox continues stagnation by almost all odds
2. The Electron mess on our desktops will claim new territory on our phones and bring security problems with it
Not very appealing. Limiting competition? When your only realistic competition is Chrome with it's 80%+ dominance, I don't think a regulator would have a problem with that.
Actually, as a tidbit, Chromium is a fork of WebKit, which is Safari's rendering engine, which for some reason started as a fork from Konqueror (KDE Linux desktop's browser).
Google did however replace the javascript engine in Chromium.
The Javascript engine in Chromium deserves a different discussion, since it also powers NodeJS.
Back in the day, WebKit was quite popular as a rendering engine and is also used by Qt.
#1 reason, and, think back to when iOS came out, was security. The knock off effect was it ensured that ios/webkit gained defacto marketshare for each device since there was no other option - as the thread starter mentions. I disagree with the contention about innovation - keeping IOS from being a minefield for 99.9999% of users I think was the right course. And killing off flash.
> I think it’s worth noting that (at least I believe) the reason apple limit the usage of other browser engines in iOS isn’t (mostly) about maintaining control and dominance. It’s about battery usage,
I disagree with this word gymnastics, it is Apple-ogism. It takes just a brief look at other decisions they've made to easily see that it is about user lock-in which fits in with their general philosophy. It is not great that they are stifling innovation at all, conflating it with browser dominance is a separate thing.
This is a specious argument. Allow competitors to deploy apps causing lousy battery life, and Safari should win easily on that basis. Apple's battery app makes it obvious when apps use a lot of energy.
Battery usage, yes, but if developers could create theirs apps as websites with no loss of functionality and pay zero money to Apple a non empty set of users would use them and Apple would lose some money. I think that Apple ultimately cares about money. Battery, PWAs, etc are all factors they ponder upon to optimize the bottom line.
>I think it’s worth noting that (at least I believe) the reason apple limit the usage of other browser engines in iOS isn’t (mostly) about maintaining control and dominance. It’s about battery usage
Why would this be a believable excuse? you can install a Firefox skin of WebKit on iOS and this skin could maybe be terrible on battery usage. A good default browser like on laptops is good enough for battery, people who care about it will use Safari, the obvious reason Apple is doing this is to prevent competition, so if Apple fucks with WebGL then you can't have say a WebGL based mobile game that would go around the Apple Store.
Even if battery usage was the reason behind it, it's not good enough. Let the user decide whether or not they're willing to sacrifice battery life if they want to.
That always sounded like very crude excuse to exert control over Web standards by them. If battery usage with their own browsers is so much better, then everyone would be using their browsers on iOS. Why even ban others?
So I don't buy any of the Apple's excuses when they actively cause anti-competitive harm.
As far as I’m aware the justification is “no executing pages you can write to at runtime” (because it’s a huge security issue). They give safari an exception to that because you can’t make a JIT without doing that, and that’s the most straightforward way to get fast JavaScript.
The Apple of today has a very conflicted relationship with webkit, the anticompetitive reasons they want to keep their platform "webkit only", simultaneously encourages them to support and neglect webkit development. i.e on the one hand, webkit must be reliable and secure and compatible "enough" to provide a decent basic browsing experience. But should not improve so much as to make developing applications competitive with the apple store.
The difference between the resources Google and Apple contribute to their respective open source browser engines is night and day, and as any web developer will know - it shows.
In an ideal world two things would change at the same time: Apple is forced to allow other browsers, and webkit gets some genuine love and decent resources to make it a legitimate competitor again, instead of being used as a pawn in a game between Apple and Google.
This list of standards also shows how Google attempts to make it even more impossible for anyone but them to maintain a browser. Shape detection API ? Seriously ? Picture-in-picture as a standard when it should be up to the OS/browser ? having the <input type="image"/> perform resizing and compression ?
We can thank WebKit and Apple's policy around it on iOS for suppressing and holding back these attempts, as sites on average still _need_ to work on an iPhone.
Shape detection is to have predictable QR code scanning across web apps, PiP as a browser API is necessary to enable it cross-platform. And image transformations are to try and collapse 100 js libraries of varying quality into a feature that people clearly want.
I’m a huge proponent of platforms aiming to be stable and largely not messing with shit but it has to be feature complete first.
In general the people making decisions on standards and implementation don't directly answer to the people honoring the Google deal. Plus, Google knows they really shouldn't stop feeding FF revenue lest they be called out, leading to bad PR and more potential antitrust lawsuits, so I don't see them stopping anytime soon.
1 is the worst possible rationale I've ever heard.
"Let's support a company that abuses its customers, developers and refuses to implement web standards just so a company that makes a far superior product doesn't gain more market share..."
They aren't advocating or supporting Apple, though. They are merely pointing out that in suchg a dire situation as the one we have now, Apple's interests partially align with consumer interests.
I think their tone makes it relatively clear that this is not a healthy state to be in!
What hyperbole! It's entirely possible for some process to be bad, and it still have (some) good consequences.
The Black Plague was terrible; but it lead to increased social mobility in the aftermath. Likewise, Apple's "one browser" policy is bad, but ironically it's the main thing stopping the other browser, Chrome, from becoming the one browser that dominates everything. I'm still against the one browser policy, as I am against the Black Plague, but a reasonable person can make these distinctions.
I view it more like the lesser of two evils. I don't like Apple's behaviour and I agree with a lot of the criticisms against their behaviour. That said, I think it's preferable to the alternative.
As someone who for quite awhile almost exclusively used Chromium based browsers and then coming back to only using but actually appreciating using Firefox I approve and very much agree with this message.
Google is up to so many sneaky things, it's stopped surprising me to find out how they're always one step ahead to make their products even more intrusive.
A new one I found out is their supposedly open-source initiative called 'Cloud Information Model' [1]. Along with others such as Salesforce, Genesys and AWS (companies that I personally don't trust), they promise 'you can create seamless and tailored personal experiences across cloud-native applications'. It's all a bit vague and fancy and sufficiently "tech-y" to impress the marketing folks but colour me suspicious.
I always wondered why the engine is not separated from the GUI in browsers. In chess world this is totally normal, you have a chess GUI and a chess engine (and a crude communication protocol).
I'll go ahead and point out the obvious that the chances of Safari going Chromium-based are high given that (1) iOS Safari sucks and (2) Microsoft has had good success with Edgium. So the likelihood of Mozilla being the only dissenting voice is high.
The chance of Apple switching from a browser engine whose security and energy profile they control completely to one built specifically to advance the goals of a competitor is somewhere close to the chance of the heat death of the universe happening in the next five minutes.
It could happen, but even if it were to happen, there would be a split from Blink in a very short time period because Google’s values and mission do not align with Apple’s values and mission.
It's a depressing situation, particularly knowing that Firefox is pretty much kept alive at Google's whim. It makes one seriously wonder whether it is feasible at all to maintain an independent open-source web browser in 2021. People tend to blame Mozilla's management and I'm sure there have been management failures but I'm not sure what they could do to make Firefox a thriving, independent, sustainable browser. It seems that the market niche of tech-capable people who value privacy and customisation over a simplified UX is not capable of sustaining Firefox on its own. So Mozilla tries to move in Chrome's direction, removing configuration options and "dumbing down" the UI, which frustrates its existing user base (including me) while apparently also failing to eat into Chrome's market share.
So what to do? Go back to being the quirky, heavily configurable browser we all know and love? That would be great for me, but even assuming Mozilla can afford to do that now (greater configurability leads to greater code complexity and therefore greater maintenance costs), experience seems to suggest it won't be enough to allow Mozilla grow its market share to a sustainable level.
Finally, and this is a bit of a tangent, but I've never quite understood why Mozilla got such a hard time from users about telemetry. I understand that telemetry is in general something to be suspicious of, but we're not talking about handing your data over to Google so they can target you with ads; we're talking about sharing technical data with a non-profit organisation to help them maintain and improve the browser you rely on. Mozilla are removing a feature you use daily? Okay, did you enable the telemetry that lets them know you use it? Receiving and analysing user data is increasingly important to delivering a good user experience. If open-source projects can't access the same data as proprietary ones do, we can't expect them to be able to react to user demands in the same way, and so we can't expect them to be able to compete in today's market.
I have to strongly agree with your last point - I also never understood the massive hard-on that the technical user-base has against useful telemetry. Perhaps it's just the loud minority, but to me it seems that most of them have never worked on an user-facing product (for-profit or not).
Yes, users can themselves explicitly communicate feedback regarding the product or its features, and no, most of them don't do that. That's why telemetry is useful.
> I also never understood the massive hard-on that the technical user-base has against useful telemetry.
> it seems that most of them have never worked on an user-facing product
If you have worked on user-facing products, then I think you do understand. I think you just don't like the answer.
Here it is in a nutshell: In the general case, how do you distinguish 'telemetry' from 'surveillance'?
And the answer is you can't, because the difference between 'telemetry' and 'surveillance' lies in the intent of the consumer of that data. Technically useful information collected in good faith today can become intrusive surveillance tomorrow with a court order, or business pivot, or just a bored insider & lack controls.
Now consider the fact that the author of every stupid new piece of code out there now seems to think it is so special it deserves to be allowed to send... who knows what back to some opaque collection endpoint as the cost of executing.
The only reactions in response to this mess that don't cost a huge amount of overhead are "block everything" and "have your way with me". Guess which a technically inclined user picks.
> I also never understood the massive hard-on that the technical user-base has against useful telemetry
Leaving your veiled insult aside, I think it's pretty easy to see but you don't want to listen to it. Namely: telemetry and surveillance are literally the same thing and the only difference lies in the goodwill of the steward of the data.
I believe we've been witnesses, dozens of times, here on HN, about yet another "private data leak" because some company can't be bothered to hire an intern for $2000 a month to do proper data and security hygiene of some meager 3-4 disks that don't even total 10TB.
So why should I trust companies by default to take good care of my data AND to use them for good only, when all the historical evidence points at them being unable to do either? Shouldn't I take the matter in my own hands? I answered yes and so I did. My PiHole black-holes anything such I can think of and until that gets criminalized I'll be freely admitting it anytime when asked.
> I have to strongly agree with your last point - I also never understood the massive hard-on that the technical user-base has against useful telemetry.
I think it would be far less hostility if we as users got access to the information ourselves. E.g. I would think it would be very useful to see stats on which features I'm using in firefox, how often, which features I'm not using, how many tabs I have (compared to the average user) etc., and I would be much more happy to share that data with firefox if I can see it first.
> I also never understood the massive hard-on that the technical user-base has against useful telemetry.
I'll leave it to others to argue why it's a privacy problem, but I'd like to push back on the "useful" and "feedback" arguments. It's appealing to say "X% of our users use this; we should prioritize it", but Mozilla has a charming history of saying "only Y% of users use this feature; we'll remove it", and for bonus points, "after we pushed this option into a really obscure sub-menu, nobody uses it, so now we can remove it while claiming that nobody cares". That is, telemetry isn't even useful for the thing that people claim it's good at, because it only provides raw data that gets used to justify things regardless of reality.
Believe me, I understand the appeal. Yesterday we were discussing something dropping support for some platforms from an open source project and the issue is... we have no way of determining how many installs are on such platforms.
Telemetry would fix this, but it's not our right to collect data from other people's machines. So our best bet would be to detect the condition we expect to cause problems, notify them in advance, and allow time for feedback before implementing a change.
Is it less pretty and a worse user experience than telemetry? Absolutely. But when you realize you have no right to data collection on someone else's machine, telemetry isn't a viable option, and we would betray people's trust by doing it.
> I also never understood the massive hard-on that the technical user-base has against useful telemetry.
People don't want to be spied on. Yes, you can find positive uses for it, but you can find positive uses for many negative technologies. If anything some of the most pervasive negative technologies also have positive uses to sweeten the pill (or even give the impression that this is a sweet and not a pill you are swallowing).
It's creepy. Like someone looking over your shoulder. Before it became normalized, that wasn't a niche opinion. I'm sure it's very useful for developing software. A camera behind me pointed at my screen might be even more useful[0]. Both are invasive and gross.
[0] Session-recording spyware "telemetry" products practically are this, and are widely used. Watching their session playback, or ability to monitor live users on "your" site (but actually, on their computer) is disturbing.
In general for applications, I usually say no to telemetry because I don't know exactly what data is being captured and how much they're stretching the truth on what it will be used for.
> greater configurability leads to greater code complexity and therefore greater maintenance costs
Firefox is extremely configurable. Settings being removed from the UI doesn't mean they are gone.
`about:config` has a crazy amount of toggles that allow customizing pretty much everything, including turning off all the Mozilla services (telemetriy, account sync, Pocket, VPN adds, ...). Compare that with the measly set of settings and undiscoverable CLI flags available in Chrome...
I personally feel removing settings from the standard UI is perfectly fine when almost no-one is using them, and power users can work just fine with settings.js or `about:config`.
about:config is removed from (not beta) android version of firefox. Who knows if they will decide to remove it on desktop as well because "only x% of our users were using about:config!"
Also if a setting is hidden behind about:config, it probably means dev will care less and less about it and eventually remove if it is becoming a hindrance
> So Mozilla tries to move in Chrome's direction, removing configuration options and "dumbing down" the UI, which frustrates its existing user base (including me) while apparently also failing to eat into Chrome's market share.
Well, no surprise there. Technical people like us experiment. Mainstream users just use what they know, and what their techie friends recommend them. They're not suddenly going to use Firefox now that it's more like chrome. They'll just use the real chrome. And they don't like touching something that works.
Note that this approach didn't work for Microsoft either (and they went a lot more 'like chrome' than Mozilla!). They're having some success with Edge but it's mainly because they push it really hard to enterprise users with their O365 integration, so people are getting to know it at work and bringing it home.
> [...] If open-source projects can't access the same data as proprietary ones do, we can't expect them to be able to react to user demands in the same way, and so we can't expect them to be able to compete in today's market.
I don't want them to become like the proprietary browsers in this regard. Telemetry is not an all-seeing oracle, it's often used to confirm their own bias because it doesn't say why the users like something or what they'd prefer. What they should be doing is listening to users instead of blindly trusting telemetry. Google and Microsoft make the same mistake but they already have a monopoly on the browser and OS markets respectively so their mistakes are easily absorbed. It's not like their products have become a lot better since they started relying on telemetry so much.
But no, I won't allow telemetry and I block it for Microsoft and Google too in my DNS. The reason I use Firefox is because I don't want to "get with the program". If I have to change my ideology, I would be changed so much that the primary reason to use Firefox is no longer relevant.
> Note that this approach didn't work for Microsoft either (and they went a lot more 'like chrome' than Mozilla!). They're having some success with Edge but it's mainly because they push it really hard to enterprise users with their O365 integration, so people are getting to know it at work and bringing it home.
Edge is also - aside from being a privacy disaster - a legitimately good product that does a lot of good UI innovation on top of stock Chrome.
Things like normie-friendly but powerful vertical tab implementations, turning menus into floating panels that can be turned into sidebars with a click, Collections etc. They're actually adding lots of customer-facing features that are really well designed.
> Finally, and this is a bit of a tangent, but I've never quite understood why Mozilla got such a hard time from users about telemetry.
That's the consequence of marketing themselves as "privacy first". Many people use Firefox because they don't want to be tracked, and therefore, any tiny bit of tracking/telemetry will be frowned upon. Google makes no such claim with Chrome, in fact, it makes it pretty clear that it tracks you.
> [..] but I'm not sure what they could do to make Firefox a thriving, independent, sustainable browser.
They could focus on building that browser, instead of getting sidetracked and wasting money on other things. Also reduce the friction of contributing to their projects from the outside, streamline the process, bring it into the 21st century while keeping top-down politics and egos out of it. I wouldn't be surprised if their rivals see more outside contributions (in total) simply because they are somewhat easier to work with.
However, overall the vast majority of contributions to Mozilla's projects is likely still coming from the outside.
Mozilla is afraid it will fail with Firefox if they don't diversify. But if Firefox fails, the world doesn't need Mozilla. If that happens they should just pack up and hand the custody of surviving technologies (Rust etc.) to someone else.
IMO they're in a good position where then can include deep-rooted privacy services on which they could (and already do in some) capitalize.
for example Mozilla VPN and Firefox Relay which added a premium version with unlimited aliases and your own @*.mozmail.com subdomain.
If they can find a way to promote themselves as a leader of Internet privacy with well-integrated servoces, and from which they can get a revenue from it then at least they'll gain some independence.
What's worse, I think it's extremely difficult, if not impossible, for another project to start from either a fork or from nothing and provide an alternative, as developing a browser (with its own rendering engine) is extremely complicated, comparable to an operating system.
The rendering engine part is kind of the least problematic bit, because there are three primary options (Gecko, WebKit, and Blink) and they're all pretty up-to-date and open source. You could also pick up Goanna, KHTML or Servo if you didn't want to use any of the big three as they're open too, but there'd be work to do on them.
There's no particularly good reason to start your own renderer from scratch.
>It seems that the market niche of tech-capable people who value privacy and customisation over a simplified UX is not capable of sustaining Firefox on its own.
>So Mozilla tries to move in Chrome's direction, removing configuration options and "dumbing down" the UI, which frustrates its existing user base (including me) while apparently also failing to eat into Chrome's market share.
You can have sensible defaults for people who value simplicity and want it to just work and have customisation accessible from the settings page for the people who want customization.
> did you enable the telemetry that lets them know you use it?
I have all telemetry and Nightly studies enabled wherever I can (unfortunately the option is unavailable in custom builds, and I use custom builds on my main OS, since I contribute code to Firefox occasionally).
> removing configuration options and "dumbing down" the UI
I never understood the whole "dumbing down" thing either. It's fundamentally the same UI as it was in Firefox 2.0 back in the day, except the menus are more well-structured (there's now a convenient hamburger rather than everything being in a crowded "application menu" bar at the top).
> I'm not sure what they could do to make Firefox a thriving, independent, sustainable browser
I think it's still all these things. But to make growth possible, they need to somehow fight against Google persistently advertising Chrome right on the fucking google dot com main page (and YouTube and so on).
> It seems that the market niche of tech-capable people who value privacy and customisation over a simplified UX is not capable of sustaining Firefox on its own.
Perhaps they could care for the automation niche. There are thriving communities on macOS who are deeply into automation, and virtually no one uses Firefox. The ones who do stop because Firefox’s AppleScript support is non-existent, while Chromium’s (and thus every browser based on it) is top notch, even better than Safari’s.
I’m not talking developers, either. Non-coders frequently cobble up short AppleScript snippets do to what they want. When they visit the forums asking for help and how to do what they want in Firefox, they are directed to the open bug report which is old enough to drink.
I have seen plenty of users abandon Firefox on account of that gap. I tried to convey that to Firefox developers multiple times—both in person and online—and their response was to not care.
If they're going to be paying developers to do it they'd need an expectation of a stronger ROI than their other efforts. I wonder if the size of the macOS automation community is large enough to make much of an impact on their market share. Would you estimate they'd gain hundreds of users? Thousands? Tens-of-thousands?
If they're relying on volunteers then they'd need a few folks with the right set of skills and a motivation to scratch that itch. I would personally love to see better AppleScript support in Firefox, but I won't judge anyone else for not stepping up if I don't have the inclination to either.
"we're talking about sharing technical data with a non-profit organisation to help them maintain and improve the browser you rely "
No we are talking about a non-profit and a for-profit at the same time, where the distinction is often not clear. But it is clear, that they included ads and "studies" by default in their browser, that did send data to whoever, without any user consent.
So no, I do not really trust them anymore. Still more than google maybe, but not enough to voluntarily send them my data. And this is a shame, because I would have liked to keep trusting them.
>but I've never quite understood why Mozilla got such a hard time from users about telemetry
Telemetry includes personal information such as IP address and some people are (rightfully) concerned about it. Also we do not know for sure what is done with this data, as Firefox server side code (the one that processes the telemetry) is not open source (and even if it was it would not be a guarantee).
> Okay, did you enable the telemetry that lets them know you use it?
There would be no problem if Firefox shipped as a zero-telemetry browser, and all telemetry was opt-in. This would remove all doubt and if you want to send Firefox data you can choose to do so.
However that is not the case. Significant amount of telemetry is enabled by default. Choosing to go for opt-out vs opt-in is what is hurting Mozilla's credibility here.
What then happens (and I am speculating here) is that this behavior triggers most power users in a negative way (for various reasons, one of them being simply using your bandwidth and resources for telemetry and noone likes having a slower browser) so they do their best to disable it. This in turn leaves Mozilla with data that does not include most of its power user base, the one that actually has most impact on Firefox market share (because as 'techies' they install the browser for their family and friends). The crippled data leads to crippled product decisions, which in turn makes power users even angrier and thus we witness the death spiral of user attrition that Firefox is currently in.
Mozilla Corporation, which represents the majority of activity on Firefox, is not a non-profit. That's only Mozilla Foundation, and it's never really been clear to me what their role is, regarding Firefox.
Mozilla Corporation is a wholly owned subsidiary of the Mozilla Foundation. There are various advantages to this kind of structure, but I don't know what they are. The upshot though is that the incentives of the owners of the Mozilla Corporation are not to squeeze every drop of profit, but rather to benefit the goals of the Mozilla Foundation (to raise money to support open source development), because the profits of the Mozilla Corporation are paid to their only shareholder: namely, the non-profit Mozilla Foundation. (No idea if they have any profits, but that's a different matter.)
Would it not be in the interest of Google as well to fund Firefox?
I would imagine they wouldn't mind spending a small amount to keep it alive to prevent accusations of Anti-competitive practises? ;)
That's how I remember it too, but I think the expectations of simplicity has changed over the years - in those days, it was closer to great defaults and no gratuitous features, whereas now it's a bit more like less flexibility (although really, Firefox has masses of options that aren't included in the UI but are accessible from about:config, so I don't really think Firefox falls victim to this criticism).
Part of the old tradeoff was that extension writers could do almost anything to make the web browser do almost anything. Nowadays, extensions are much less flexible. I think for good reason: being able to click a few buttons and get pwned isn't really a desirable feature. But the tradeoff has moved. I don't think that's really an argument against Firefox, but consider that powerusers are often very conservative, I'm not surprised that it caused some disagreement.
The only thing I know of that's similar to that is how Mozilla has Google Analytics on some pages as part of the Firefox interface, but there they have a contract restricting how the data is used: https://bugzilla.mozilla.org/show_bug.cgi?id=697436#c14
(Disclosure: I work for Google, speaking only for myself)
> particularly knowing that Firefox is pretty much kept alive at Google's whim.
This is simply not so. Google pays to be the default search engine on Firefox because it is beneficial for them. Had they not, this place would be bought out by Bing or whoever else, and in the end Google will lose more.
it would be great if we can move past the browser and debundle the tech, for example we should have a few different JS engines, a few different CS engines and a multitude of different GUIs ...
> So Mozilla tries to move in Chrome's direction, removing configuration options and "dumbing down" the UI, which frustrates its existing user base (including me) while apparently also failing to eat into Chrome's market share.
The funny thing about this is that it's a narrative, but is it correct? Configuration options may be low, but Chrome has added things like tab groups and a reading list / bookmarks sidebar. They're in no way aiming to be as customizable as Vivaldi/presto!Opera/xulExtensions!Firefox, but even stock Chrome is actually adding useful features, while most news I've seen from Firefox have been them removing unique features I've used and loved, like being able to sync keyword searches via bookmarks.
The only significant feature I've seen them add - and it's a doozy, I admit - is Containers. But that's cold comfort when other features get removed at a steady rate.
> It seems that the market niche of tech-capable people who value privacy and customisation over a simplified UX is not capable of sustaining Firefox on its own.
This may be true, but it can really come down to quality of product: Firefox is losing ground, but Brave for example is growing, and doing it by a privacy sales pitch (with some dumbfucks who think they're going to get rich off BAT added in - it's a cut from Brave's ad revenue, ffs, and individual ad viewers aren't worth shit except en masse when the money pools up at creators' and ad agencies' wallets).
> Okay, did you enable the telemetry that lets them know you use it? Receiving and analysing user data is increasingly important to delivering a good user experience. If open-source projects can't access the same data as proprietary ones do, we can't expect them to be able to react to user demands in the same way, and so we can't expect them to be able to compete in today's market.
This is true, but making decisions purely off telemetry stats and setting up self-fulfilling prophecies of making features harder to find and then saying nobody uses them isn't exactly the way either. Telemetry is a good jumping off point, I think, but as a sole director it's shit precisely because privacy-conscious users are going to turn that shit off if they can out of habit.
> I've never quite understood why Mozilla got such a hard time from users about telemetry.
I think a lot of the Mozilla userbase is from an earlier age, before everything became cloud-based subscription services. They long for the days of locally installable software, buying new versions vs. subscribing to an app, etc. Some are the kind of obstinate FOSS purists who'd use gNewSense even if it meant they had to use their computer as a command line only device.
Think about Pocket, for example. I was one of the abovementioned people and hated its inclusion, and people still grumble about it in part due to the source code, in part just due to the old bad blood.
They'd essentially need a relaunch with a new take and attitude - look at Brave, whose pitch is pretty similar, and how people are a-ok with monetized services within the browser so long as they're opt-in. The product's newer, and so the attitude people come to it is newer. And it's growing.
Finally, there's an issue of focus: The organization increasingly feels like general activists first, custodians of a product second, which is not a vibe much of the competition gives off. Actors like Brave and Vivaldi have firm, in some sense political stances, but they're of a narrower sort of user control and privacy. I know people at both orgs who do/have shown their politics, but it doesn't show at the org/product level. The user? Does. I never, ever want to hear shit like "we need more than deplatforming" from an ostensibly privacy and user centered organization.
I think part of this discussion needs to be that Firefox, while open source, doesn't provide footing for the community to build browser forks the way Chromium does. This sort of open usage, ironically, feels very fitting to the spirit of Firefox, but they're not even close to Chrom(e|ium).
I've been building a browser full time the past year+ (synth.app) and FF core wasn't really even an option. They've done very little to make the engine usable outside of Firefox.
Now I'm sure there are a variety of savory and unsavory things that led here, but building that stuff out seems like a good way to grow the ecosystem. At least they would've had a chance at capturing the Brave/Opera/Edge/etc market and those seats at the committees.
This isn't to say that I'm not worried about these standards merging like this. I've spent many hours working out weird chromium only behaviors that websites rely on these days to do things (and egregiously so if they detect an agent remotely resembling chrome).
That's a real missed opportunity. Firefox would have made a fantastic embedded webview, and could have plausibly become the core of Electron. Back when webviews were IE, with atrocious Javascript support and all the usual IE quirks, Firefox was a superior product and interconnecting with other software is very in line with the open source ethos.
Enough features to distinguish on, enough political/managerial reasons for choosing an independent FLOSS engine over one controlled by Google.
Sure, Edge/MS won't move to this engine anywhere soon. Nor will Brave switch over tomorrow, or electron rebuild around their tooling. But the world is full or "HTML-2-PDF renderers, headless testing toolkits, (embedded) webview-libraries or electron-alike toolkits, which are now almost all exclusively Chromium based.
I think that is a problem many open source programs have, and could improve.
A lot of GUI based programs should think of implementing parts of it as a library others can use. I remember early Git implementations in IDEs where they just ran git commands in the background and parsed the command line output. Imagine if the same had been done with SQLite, would it still be as popular today?
I don't have much experience with creating desktop software, but it seems to me that separating the GUI from the "engine" would bring other benefits too.
I have often looked at OSS and wanted to use parts of it myself. An email client might have a really good mail parser that handles encoding, attachments etc. But decoupling it from the rest of the program would take too much time.
> ... weird chromium only behaviors that websites rely on these days to do things (and egregiously so if they detect an agent remotely resembling chrome).
oh man. I need to find some time to write about how bad it is.
The gnarliness spans the whole stack. From weird java-applet like API escalation behavior if chrome is detected (e.g. Google properties feature gate a ton around this) to how there is not even a clear way to get a DRM license for a custom browser without waiting for Google indefinitely [1].
Here's a challenge: fire up a chromium fork and get it to run a relaxed DRM website like Netflix. If you get that far now try loading HBOMax with their fingerprinting/DRM protection on top. I'm not even sure it'd be possible in FF (at least without some DRM piggy backing if there isn't one).
Yup, as someone who worked on fixing issues with IE5/IE6/IE7 behaviours I definitely feel the slow burning fire of Chrome repeating that whole saga once again. And probably in a much more painful way given the explosive growth of the internet and browsers since the early 2000s (I started working with web dev around 2005).
Servo wasn't a fork, nor was it meaningfully a "community" project - sure there were community contributors (it was a fun project to hack on) but most of the meaty work was being done by Mozilla employees.
I wonder how difficult would be an open source community project whose explicit aim would be to take the Firefox code base and make it more modular and embeddable, like Chromium? Would it be too much work for a community effort?
Even if possible, such an initiative could only be successful if Mozilla supports it otherwise the “new” code will quickly go out of sync with the Firefox codebase.
> Firefox, while open source, doesn't provide footing for the community to build browser forks the way Chromium does.
This reminds that Wine uses Mozilla code for their Internet Explorer replacement (wine-gecko). I wonder how far behind Firefox's rendering engine that code is, and how much effort is involved for the Wine maintainers.
I used to hold the same opinion: Google controls the world because everything is Blink/Chromium based! Must use Firefox to protest!
Then I looked closer look at the history of Chromium and Blink.
The reality is that a lot of the other "Chromium-based" browsers actually only use the Blink renderer. They don't use many (if any) other Chromium components other than probably V8.
In ancient times, Blink itself was a fork of Webkit. So, does that mean Apple controls everything?? But Webkit actually came from KDE's KHTML, didn't it.. Linux wins...
The kicker for me is: Blink and V8 are open source, and anyone can fork them at any time. Because of this, Microsoft, Oracle, Brave - every "Chromium" based browser vendor is contributing code. So does Google really control us that much? Blink and V8 make a rock solid browser core and are being worked on by a lot of companies, not just Google. It's like the Linux kernel - kind of a marvel of open source. Not something we need to fight against so viciously, in my opinion.
(Edit: "rock solid" might sound extreme to some... The HTML and JS specs are absurdly complex to the point where there's basically no hope of anyone implementing them from 0. There's a lot of bloat in modern web, no doubt. But if you're really worried about crazy JS features cluttering your browsing experience, you can go clone the Chromium source and pull out the crap you don't like.)
Yes. Contributing code to something doesn't mean that you suddenly control the direction of that thing. Google still makes the big decisions about what gets to enter the codebase: which web features to support, which ones to deprecate, how to interpret standards, and how to slowly align the web with their own financial incentives.
>Yes. Contributing code to something doesn't mean that you suddenly control the direction of that thing.
I think the idea of gp's point about others forking code means the forkers can also influence the code because they control the fork.
Otherwise, if we take your comment at face value, we'd conclude that Google's contributions to Webkit means it can't "suddenly control the direction" of Apple's Webkit. That's true, but also becomes irrelevant because Google controls its fork of "Blink".
In other words, does Apple's Webkit control us that much? No, because it seems like Google's Blink/Chromium is sufficiently independent. If we go back farther in the timeline, are we concerned that KHTML controls us? No, because it seems like Apple's fork of Webkit is independent and not beholden to KHTML decisions.
If Microsoft really wanted to, it seems like they have the resources to do what Apple did to KHTML and what Chrome did to Webkit.
True. People forgot that Microsoft had been developing its own browser for years before they moved to Chromium. That team and expertise didn't just disappear. They've been doing significant work in that code base. See https://twitter.com/ericlaw/status/1329200077517295618 from a year ago. Having that technical power does give them quite a lot of control over the code base which can help balance the political power here.
> They care about having a simple, fast browser who just works.
And the "just works" part won't happen without the other browsers' competition. It will become "just works with other Google products, for those who hold the same values as Google holds".
In fact, what's often forgotten is that even before MS's illegal monopolization, IE dominated Netscape because it was genuinely better.
But a few short years later it was regular end users who were suffering due to IE and it's lack of competition, which led to MS sleeping on it and letting security issues (both technical and social) pile up.
Exactly. So what if Google controls the internet experience through Chromium. The user will have to pay someone eventually. Firefox is not a free magic bullet.
On the other hand, much bigger problems in the world, so we go build something else instead of reinventing what Google has already built.
KDE relies heavily on the Qt libraries and Qt is using Blink in their QtWebEngine[1]. There's even a web browser called Falkon (The KDE browser, kind of) that uses this library[2].
The real problem of Firefox is one that nobody cares about: distribution.
Let's say Firefox is the most advanced browser of the universe. How can you get people to install Firefox?
Chrome has the advantage here because it is preinstalled in every Android phone and Android has more than 90% market share.
The second advantage Chrome has is that it cannot be uninstalled from Android. The fact that Android phones have a limited storage space is a compelling reason to not install a second browser.
The third advantage Chrome has is the fact that more than 90% of people use Google has search engine and every time you access google.com with a browser other than Chrome you get a "Switch to Chrome" notification telling you that Chrome will help you "hide" annoying ads (without telling you that Google is responsible for the annoying ads) and you will be safe against malware. The regular user fears malwares and viruses more than ads or anything else because they think their bank account info will be stolen, so better security is a compelling reason to install Chrome.
Please, tell me, how do Firefox or any other browser can compete with the fact that Google is abusing their dominance of the search engine market and the mobile phone market to "force" people to use Chrome?
Firefox had more than 30% market share at their peak, against pre-installed IE and Microsoft aggressive tactics. It was before the ballot screen.
Together with Chrome, they ended up beating IE, at the time neither had a significant advantage in distribution, at least compared to IE.
So in theory, Chrome can be beaten, except that unlike IE, Chrome doesn't suck, in fact, about the only thing going for Firefox is that it is not Chrome.
Well, the engine has to be there for all the apps that use a WebView and are expecting Chromium to embed that webview (in terms of utilizing any css/js quirks so that the experience is guaranteed consistent across vendors), so "deleting" chrome wouldn't do anything more than how deleting Safari on iOS just hides the app icon away [in App Library].
I don't disagree with this comment, but it's worth noting Chrome was already rising to dominance as a desktop browser before Android/mobile internet usage became a significant factor.
Somehow even with Microsoft promoting IE on their platform, people still chose to install an alternative.
Internet Explorer used to have that edvantage - included in Windows but most people used it to download Chrome because Chrome was better in various ways. I think the problem with Firefox is it's not noticeably better. Not sure how you fix that though.
> For me Firefox is the only alternative to a complete Chrome hegemony in the sense that:
> it’s open-source in the real sense (a project that’s truly community-driven)
I missed when the community wanted to do away with tab groups, compact mode, or keyword searches synced via bookmarks. The project is handled by a corporation with a multimillion dollar advertising deal with one of the EvilCorps. Uhh, yeah.
> it has a great track record of fighting for its users and for a better Internet.
Last I checked, it's owned by a foundation that's very okay with advocating that others tell me what I should see on the 'net. "We need more than deplatforming" are not words I ever want to hear from a privacy organization's mouth. That and "fighting for its users" don't exactly go together, unless you believe the Foundation's purpose is to be its users' moral custodian in matters that are not tech-related.
The whole sales pitch of this thing is "you should use a browser that increasingly sucks, that's increasingly lacking in support, whose stewards get their money from EvilCorp and cheerfully advocate for Internet censorship, all because they use a different browser engine". When my option would be to use browsers that do not suck and actually improve release by release, have revenue streams not so beholden to EvilCorp and put their makers' personal politics aside for user control and privacy.
> Last I checked, it's owned by a foundation that's very okay with advocating that others tell me what I should see on the 'net. "We need more than deplatforming" are not words I ever want to hear from a privacy organization's mouth.
Ugh, I dislike the title of that post. I still claim that you're misinterpreting it, though. It should have been something like "We need better answers than deplatforming." Deplatforming is not the answer, and we need better ones.
Sometimes deplatforming is the right answer. Not when it's about a political agenda, but there are many many actually harmful uses out there, many of them illegal, and ignoring those on your platform is the same as facilitating them. But deplatforming is about as effective as sticking your finger in a dike for truly improving things.
In my opinion, Mozilla has done a decent job of being apolitical when possible. Yes, it does think you shouldn't see some things on the 'net, but those things are things like scams and malicious disinformation. It does not say that you should not see the latest blatherings of Trump or whoever, except perhaps when they're directly encouraging violence or sedition.
> In my opinion, Mozilla has done a decent job of being apolitical when possible. Yes, it does think you shouldn't see some things on the 'net, but those things are things like scams and malicious disinformation. It does not say that you should not see the latest blatherings of Trump or whoever, except perhaps when they're directly encouraging violence or sedition.
> The change resulted in an increase in Facebook traffic for mainstream news publishers including CNN, NPR and The New York Times, while partisan sites like Breitbart and Occupy Democrats saw their numbers fall.
The entire post reeked of political tribalism in a way I don't like from people who make my tools. While seeing less Breitbart and Occupy Democrats might be welcome, Mozilla were completely fine with third parties boosting the visibility of openly partisan organizations who'll happily lie to my face. No, no thanks.
> I missed when the community wanted to do away with tab groups, compact mode, or keyword searches synced via bookmarks. The project is handled by a corporation with a multimillion dollar advertising deal with one of the EvilCorps. Uhh, yeah.
Hm? When were keyword searches or compact mode removed? I’m still using them in 94.0
> "We need more than deplatforming" are not words I ever want to hear from a privacy organization's mouth.
Any entity participating in a democratic society should be allowed to voice their support for keeping said society healthy. Antivaxxers and "the vote was stolen!!!" putsch supporters are a direct threat towards society itself.
There are things in a society where standing "impartially" aside is taking a stand in itself - a stand on the side of those who want to destroy society.
> Unlimited tolerance must lead to the disappearance of tolerance. If we extend unlimited tolerance even to those who are intolerant, if we are not prepared to defend a tolerant society against the onslaught of the intolerant, then the tolerant will be destroyed, and tolerance with them
~ Karl Popper, The Open Society and Its Enemies, 1945
> Clearly, that market share was lost solely to Chrome & co.3 I can attribute this decline to various factors:
>Google’s massive development resources and marketing machine.
>Most people not thinking about the long-term ramifications of ending up in a market with a single vendor in it.
>Firefox losing its status of a shiny new thing over the years.
>Mozilla’s inability to capitalize on the popularity of Firefox in the past. I think almost all of their revenue came from a search deal with Google.
The true reasons Firefox lost market share are:
1. Firefox has become a mess
2. Mozilla is terribly mismanaged
To see Firefox thrive, we have to push towards management change while there's still something to be saved or by forking Firefox
The true reasons Firefox lost market share is because we, developer & tech people started to install Chrome on family computers instead of Firefox because it was safer & faster (way way faster). And we never came back from it.
When Chrome came out, it was way better. Now I don't really see big difference in performance, they have similar extensions, frequent updates, sync, etc.
I prefer Firefox but I don't really need to install it on family computers because whatever browser they use is probably good enough.
"developer & tech people started to install Chrome on family computers instead of Firefox..."
I'm not so certain those numbers compare with the 10s of millions of people(100s?) who's default browser was hijacked by nefarious bundles in every 3rd party installer under the sun back in the 2000s and early 2010s.. Those people knew no better and have been conditioned(or just don't care) to continue whatever gets them interneting.
Why would I even want to install Firefox on my families computer? The thing is, I want them to have a long term, good working solution that doesn't become a pain in my ass. Firefox isn't very stable for non-tech people, that's the sad truth. Mozilla is badly missmanaged, they are killing Mozilla and specially Firefox. Things need to change, badly.
>The true reasons Firefox lost market share is because we, developer & tech people started to install Chrome on family computers instead of Firefox because it was safer & faster (way way faster). And we never came back from it.
Which comes down to the reasons I've already stated.
Those reasons might have applied half a decade ago. I was one of the early adopters of chrome and I've since switched back to Firefox for a better experience
Do you truly, honestly believe that being preinstalled on Android and ChromeOS, advertised specifically to Firefox users on the homepage of the #1 most visited website in the world (google.com, and it was literally the only ad that has ever been allowed there), and shoved into all kinds of installers for Antivirus, Adobe, Java and so on with the "make Chrome my default browser" button automatically checked --- all of that had nothing to do with the "true reason" Firefox has been trending down?
The marketing campaign for Chrome alone, if it is even possible to assign a dollar value to it, would have cost billions of dollars for anyone other than Google.
End users don't care about the management of firefox being messy or not. They install the web browsers that are advertised at them. Every time they go to a youtube link or to their gmail inbox there is a banner ad to install google chrome. Corporate IT now installs google chrome by default on work hardware at a lot of organizations because it works out of the box with their google business products, so you are familiar with google chrome from the workplace or even in schools with chromebooks now too. Google has millions of dollars more to blow than Mozilla at this sort of arms race and its shown in the market share.
Firefox is compromised by the fact it’s core active users are also its largest liability. It’s the innovators dilemma. They want it to (more or less) stay the same and not move forward and make changes to compete with Chrome. Whereas for them to achieve a larger market share it needs a radical overhaul. Really what Mozilla need to do is build a “new browser” called something different and put their weight behind that. I thought they were on that path with Servo and the HTML based UI they were developing for it, but I think they bit off more than they could chew and did not move quickly enough.
The tight relationship between rendering engine and browser has been broken by Chrome and its “children” (and in some way also by Apples enforced usage of their WebKit implementation in ios). Mozilla need to follow suit in order to survive, rip that rendering engine out, build a new browser and a “browser toolkit” to let other people build their own.
> They want it to (more or less) stay the same and not move forward and make changes to compete with Chrome.
Most of the negative feedback from users comes from two paths, changes that break add-ons, changes that remove customization. Either of those two effectively reduce the value proposition, so I think negative feedback is granted.
The problem most 'core' users have is this UX ethos that some how we are not having more MAUs because we fail to "make changes to compete with Chrome". This has penetrated the Firefox team and has lead to a copy cat of UX features from Chrome and a 'dummyfication' of UX.
The reason Firefox is unable to compete with Chrome or Edge is not because of missing features or performance. Both Firefox and Edge have million dollar advertisement and OEM agreements. Talk to anybody on the street and everyone and their dog will know Chrome, Firefox not so much. The average users will use whatever is pre-installed. They will not go out of their way because of Chrome-like features.
This causality that somehow Firefox is missing market share because of features or UX is flawed. Firefox is playing a Goliath and David game, with billion dollar revenue companies. Accepting and embracing it's niche nature is a necessary first step.
I can see that, I was using fairly broad strokes in first part of my original comment.
I think it’s the second part that is more important than my initial (potentially unfair) generalisation.
In order to fund further development of gecko it needs to become a competitor to WebKit/blink and grab that market share in this new world of many browser front ends that are cropping up. Explore new business models, for example sign revenue share agreements with new browser developers in exchange for supporting (or even helping with initial funding) their development.
> They want it to (not or less) stay the same and not move forward
I don't think this is true at all. Anecdotally, a lot of Firefox users have been very receptive towards recent changes. Quantum was a huge success and I know very few people that miss the old Firefox with all of its jank.
> Mozilla need to follow suit in order to survive, rip that rendering engine out, build a new browser and a “browser toolkit” to let other people build their own
This is precisely what Servo is: https://servo.org/. Mozilla know what they're doing.
I believe they laid off the Servo development team?
Also they moved way to slowly with Servo, starting it as a research project was correct. But they should have gone all in on it years ago.
I know they have taken parts of it and folded them into Firefox, but it should have been the the other way round. Take the bits of Firefox they could and combine them into something new with Servo.
This sounds like a broad generalization. I have been a Firefox user for many years and I'm happy to see it compete with updates. I like seeing it change.
> The tight relationship between rendering engine and browser has been broken by Chrome and its “children” (and in some way also by Apples enforced usage of their WebKit implementation in ios). Mozilla need to follow suit in order to survive, rip that rendering engine out, build a new browser and a “browser toolkit” to let other people build their own.
Exactly. I would really like to use something google-free, but the interface
of Qutebrowser is too good, and Qutebrowser can't use Mozilla's rendering
engine, even though the developers would like to.
Maybe we should better ask the question why a browser dupoly is bad and what we expect from a competing browser.
I think the core goal is influence: The ability to meaningfully change the web ecosystem or counteract changes that would be harmful.
Of course market share is necessary for influence, but I don't think it's sufficient: If Firefox gained a larger market share but at the cost permanently catching up to Chrome, I don't think a lot would be won.
> Really what Mozilla need to do is build a “new browser” called something different and put their weight behind that
Mozilla brand has value in privacy, not browsers. It could start VPN, cloud services, remote backups, smart home, security cameras... Even Android phones with stamp from Mozilla would be great.
There are no money in browsers, it is basically a feed tube from big corporation to its drones. Mozilla should not sponsor large corporations.
What makes Firefox seem less polished to you than chrome? When I use chrome, the feeling I get is one of standing in an unfurnished office space with white walls and few windows. To me, that is the opposite of polished.
Firefox in comparison feels like being in a grand old house that was built before plumbing and electricity. You can tell that it used to be beautiful and polished, but the luster has faded over time.
> Firefox is compromised by the fact it’s core active users are also its largest liability. It’s the innovators dilemma. They want it to (more or less) stay the same
How much of the users are actually technical?
The Firefox user share is frequently seen through the lens of technical features, however, I have the suspicion that the vast majority of the audience is regular users who have no idea of anything technical.
Two things that I think are worth calling out:
1. In many ways Apple's anti-competitive behaviour on iOS/iPadOS is a blessing. It's one of the few things that keep Chromium's dominance in check. Of course, it's not great that Apple are stifling innovation like this, but consider the alternative: Chromium dominance on all platforms.
2. Why it's worth caring about this at all? So what if Chromium is the only engine, it would make things easier for developers after all. To this I say, go read some of the discussions in standard bodies(for example about FLoC). Engineers from Apple and Mozilla are largely our bastion against Google's harmful proposals for the web. Pushback from Apple and Mozilla are only relevant as long as they have market share to speak of. The recent lawsuit against Google(summary[0]) by many US states should be extremely worrying to anyone that cares about the open web and it should make handing over any more control to Google a terrifying prospect.
Mozilla maintains a list[1] of their positions on various standard suggestions that is also a useful resource.
0: https://twitter.com/fasterthanlime/status/145205393819534131...
1: https://mozilla.github.io/standards-positions/
Whether they do have ulterior motives or not, the effect is that innovation is stifled.
Remember that Apple doesn't allow other web browser engines in any application. Imagine if an Electron application on iOS just decided to ship with it's entire, own browser engine. We would have super-bloated apps like our desktops, and if a security flaw was found, good luck getting all those apps to update.
In a way, Apple knows that allowing other browser engines means:
1. Chromium-based browsers just increase their monopoly, Firefox continues stagnation by almost all odds
2. The Electron mess on our desktops will claim new territory on our phones and bring security problems with it
Not very appealing. Limiting competition? When your only realistic competition is Chrome with it's 80%+ dominance, I don't think a regulator would have a problem with that.
I disagree with this word gymnastics, it is Apple-ogism. It takes just a brief look at other decisions they've made to easily see that it is about user lock-in which fits in with their general philosophy. It is not great that they are stifling innovation at all, conflating it with browser dominance is a separate thing.
Why would this be a believable excuse? you can install a Firefox skin of WebKit on iOS and this skin could maybe be terrible on battery usage. A good default browser like on laptops is good enough for battery, people who care about it will use Safari, the obvious reason Apple is doing this is to prevent competition, so if Apple fucks with WebGL then you can't have say a WebGL based mobile game that would go around the Apple Store.
I wish all phone manufacturers actually understood that
/me glances at my Pixel 3XL with 3430 mAh batt
So I don't buy any of the Apple's excuses when they actively cause anti-competitive harm.
Deleted Comment
Deleted Comment
The difference between the resources Google and Apple contribute to their respective open source browser engines is night and day, and as any web developer will know - it shows.
In an ideal world two things would change at the same time: Apple is forced to allow other browsers, and webkit gets some genuine love and decent resources to make it a legitimate competitor again, instead of being used as a pawn in a game between Apple and Google.
I’m a huge proponent of platforms aiming to be stable and largely not messing with shit but it has to be feature complete first.
for better or worse, Apple has been the single biggest driver towards privacy enhancement.
There's new headlines about this every few months.
https://blog.mozilla.org/en/privacy-security/privacy-analysi...
https://www.howtogeek.com/756338/mozilla-says-chromes-latest...
There's also this:
https://blog.mozilla.org/blog/2020/08/04/latest-firefox-roll...
https://twitter.com/__jakub_g/status/1365400306767581185
And the top comment of the hacker news thread associated with that last link?
>My friend who works in an adtech company:
>"Protip: Use Firefox instead of Chrome. We get very little data from Firefox users"
"Let's support a company that abuses its customers, developers and refuses to implement web standards just so a company that makes a far superior product doesn't gain more market share..."
I think their tone makes it relatively clear that this is not a healthy state to be in!
The Black Plague was terrible; but it lead to increased social mobility in the aftermath. Likewise, Apple's "one browser" policy is bad, but ironically it's the main thing stopping the other browser, Chrome, from becoming the one browser that dominates everything. I'm still against the one browser policy, as I am against the Black Plague, but a reasonable person can make these distinctions.
Apple customers are generally pretty happy with their hardware and software.
Brave also deserves a mention. As long as Brave exists in its current form, there will be a version of Chromium without Google’s “bad” stuff.
It sure would, but here just as in many areas of tech, developer convenience is diametrically opposed to what's good for users.
A new one I found out is their supposedly open-source initiative called 'Cloud Information Model' [1]. Along with others such as Salesforce, Genesys and AWS (companies that I personally don't trust), they promise 'you can create seamless and tailored personal experiences across cloud-native applications'. It's all a bit vague and fancy and sufficiently "tech-y" to impress the marketing folks but colour me suspicious.
EDIT: forgot the link,
1: https://cloudinformationmodel.org/faq/
For WebKit that's the case.
Mozilla existing (and shipping spyware, just like Chrome) doesn't really do anything to stop any of that.
It could happen, but even if it were to happen, there would be a split from Blink in a very short time period because Google’s values and mission do not align with Apple’s values and mission.
So what to do? Go back to being the quirky, heavily configurable browser we all know and love? That would be great for me, but even assuming Mozilla can afford to do that now (greater configurability leads to greater code complexity and therefore greater maintenance costs), experience seems to suggest it won't be enough to allow Mozilla grow its market share to a sustainable level.
Finally, and this is a bit of a tangent, but I've never quite understood why Mozilla got such a hard time from users about telemetry. I understand that telemetry is in general something to be suspicious of, but we're not talking about handing your data over to Google so they can target you with ads; we're talking about sharing technical data with a non-profit organisation to help them maintain and improve the browser you rely on. Mozilla are removing a feature you use daily? Okay, did you enable the telemetry that lets them know you use it? Receiving and analysing user data is increasingly important to delivering a good user experience. If open-source projects can't access the same data as proprietary ones do, we can't expect them to be able to react to user demands in the same way, and so we can't expect them to be able to compete in today's market.
Yes, users can themselves explicitly communicate feedback regarding the product or its features, and no, most of them don't do that. That's why telemetry is useful.
> it seems that most of them have never worked on an user-facing product
If you have worked on user-facing products, then I think you do understand. I think you just don't like the answer.
Here it is in a nutshell: In the general case, how do you distinguish 'telemetry' from 'surveillance'?
And the answer is you can't, because the difference between 'telemetry' and 'surveillance' lies in the intent of the consumer of that data. Technically useful information collected in good faith today can become intrusive surveillance tomorrow with a court order, or business pivot, or just a bored insider & lack controls.
Now consider the fact that the author of every stupid new piece of code out there now seems to think it is so special it deserves to be allowed to send... who knows what back to some opaque collection endpoint as the cost of executing.
The only reactions in response to this mess that don't cost a huge amount of overhead are "block everything" and "have your way with me". Guess which a technically inclined user picks.
Leaving your veiled insult aside, I think it's pretty easy to see but you don't want to listen to it. Namely: telemetry and surveillance are literally the same thing and the only difference lies in the goodwill of the steward of the data.
I believe we've been witnesses, dozens of times, here on HN, about yet another "private data leak" because some company can't be bothered to hire an intern for $2000 a month to do proper data and security hygiene of some meager 3-4 disks that don't even total 10TB.
So why should I trust companies by default to take good care of my data AND to use them for good only, when all the historical evidence points at them being unable to do either? Shouldn't I take the matter in my own hands? I answered yes and so I did. My PiHole black-holes anything such I can think of and until that gets criminalized I'll be freely admitting it anytime when asked.
I think it would be far less hostility if we as users got access to the information ourselves. E.g. I would think it would be very useful to see stats on which features I'm using in firefox, how often, which features I'm not using, how many tabs I have (compared to the average user) etc., and I would be much more happy to share that data with firefox if I can see it first.
Once upon a time, Firefox probably had a normal ratio of privacy-conscious users to privacy-indifferent users.
But if the privacy-indifferent users are increasingly lost to Chrome, FF is probably left with an unusually privacy-conscious userbase.
I'll leave it to others to argue why it's a privacy problem, but I'd like to push back on the "useful" and "feedback" arguments. It's appealing to say "X% of our users use this; we should prioritize it", but Mozilla has a charming history of saying "only Y% of users use this feature; we'll remove it", and for bonus points, "after we pushed this option into a really obscure sub-menu, nobody uses it, so now we can remove it while claiming that nobody cares". That is, telemetry isn't even useful for the thing that people claim it's good at, because it only provides raw data that gets used to justify things regardless of reality.
Telemetry would fix this, but it's not our right to collect data from other people's machines. So our best bet would be to detect the condition we expect to cause problems, notify them in advance, and allow time for feedback before implementing a change.
Is it less pretty and a worse user experience than telemetry? Absolutely. But when you realize you have no right to data collection on someone else's machine, telemetry isn't a viable option, and we would betray people's trust by doing it.
People don't want to be spied on. Yes, you can find positive uses for it, but you can find positive uses for many negative technologies. If anything some of the most pervasive negative technologies also have positive uses to sweeten the pill (or even give the impression that this is a sweet and not a pill you are swallowing).
[0] Session-recording spyware "telemetry" products practically are this, and are widely used. Watching their session playback, or ability to monitor live users on "your" site (but actually, on their computer) is disturbing.
In case of mozilla specifically telemetry didn't help them to not destroy firefox's UI.
Dead Comment
Firefox is extremely configurable. Settings being removed from the UI doesn't mean they are gone.
`about:config` has a crazy amount of toggles that allow customizing pretty much everything, including turning off all the Mozilla services (telemetriy, account sync, Pocket, VPN adds, ...). Compare that with the measly set of settings and undiscoverable CLI flags available in Chrome...
I personally feel removing settings from the standard UI is perfectly fine when almost no-one is using them, and power users can work just fine with settings.js or `about:config`.
Also if a setting is hidden behind about:config, it probably means dev will care less and less about it and eventually remove if it is becoming a hindrance
Well, no surprise there. Technical people like us experiment. Mainstream users just use what they know, and what their techie friends recommend them. They're not suddenly going to use Firefox now that it's more like chrome. They'll just use the real chrome. And they don't like touching something that works.
Note that this approach didn't work for Microsoft either (and they went a lot more 'like chrome' than Mozilla!). They're having some success with Edge but it's mainly because they push it really hard to enterprise users with their O365 integration, so people are getting to know it at work and bringing it home.
> [...] If open-source projects can't access the same data as proprietary ones do, we can't expect them to be able to react to user demands in the same way, and so we can't expect them to be able to compete in today's market.
I don't want them to become like the proprietary browsers in this regard. Telemetry is not an all-seeing oracle, it's often used to confirm their own bias because it doesn't say why the users like something or what they'd prefer. What they should be doing is listening to users instead of blindly trusting telemetry. Google and Microsoft make the same mistake but they already have a monopoly on the browser and OS markets respectively so their mistakes are easily absorbed. It's not like their products have become a lot better since they started relying on telemetry so much.
But no, I won't allow telemetry and I block it for Microsoft and Google too in my DNS. The reason I use Firefox is because I don't want to "get with the program". If I have to change my ideology, I would be changed so much that the primary reason to use Firefox is no longer relevant.
Edge is also - aside from being a privacy disaster - a legitimately good product that does a lot of good UI innovation on top of stock Chrome.
Things like normie-friendly but powerful vertical tab implementations, turning menus into floating panels that can be turned into sidebars with a click, Collections etc. They're actually adding lots of customer-facing features that are really well designed.
That's the consequence of marketing themselves as "privacy first". Many people use Firefox because they don't want to be tracked, and therefore, any tiny bit of tracking/telemetry will be frowned upon. Google makes no such claim with Chrome, in fact, it makes it pretty clear that it tracks you.
They could focus on building that browser, instead of getting sidetracked and wasting money on other things. Also reduce the friction of contributing to their projects from the outside, streamline the process, bring it into the 21st century while keeping top-down politics and egos out of it. I wouldn't be surprised if their rivals see more outside contributions (in total) simply because they are somewhat easier to work with.
However, overall the vast majority of contributions to Mozilla's projects is likely still coming from the outside.
Mozilla is afraid it will fail with Firefox if they don't diversify. But if Firefox fails, the world doesn't need Mozilla. If that happens they should just pack up and hand the custody of surviving technologies (Rust etc.) to someone else.
for example Mozilla VPN and Firefox Relay which added a premium version with unlimited aliases and your own @*.mozmail.com subdomain.
If they can find a way to promote themselves as a leader of Internet privacy with well-integrated servoces, and from which they can get a revenue from it then at least they'll gain some independence.
I started using Relay recently and it seems useful. I'll subscribe. I hope they can get a few hundred thousand paying users there...
Start by fixing low-hanging frukt (the tab-strip api, make real customizability for the UI possible again) and build momentum from there.
I'm ready to pay a bit for what is one of my most important tools, and I think we all should think about it that way.
Just don't start growth hacking me or anything sleazy and I'm also your free billboard on HN and elsewhere.
There's no particularly good reason to start your own renderer from scratch.
>So Mozilla tries to move in Chrome's direction, removing configuration options and "dumbing down" the UI, which frustrates its existing user base (including me) while apparently also failing to eat into Chrome's market share.
You can have sensible defaults for people who value simplicity and want it to just work and have customisation accessible from the settings page for the people who want customization.
I have all telemetry and Nightly studies enabled wherever I can (unfortunately the option is unavailable in custom builds, and I use custom builds on my main OS, since I contribute code to Firefox occasionally).
> removing configuration options and "dumbing down" the UI
I never understood the whole "dumbing down" thing either. It's fundamentally the same UI as it was in Firefox 2.0 back in the day, except the menus are more well-structured (there's now a convenient hamburger rather than everything being in a crowded "application menu" bar at the top).
> I'm not sure what they could do to make Firefox a thriving, independent, sustainable browser
I think it's still all these things. But to make growth possible, they need to somehow fight against Google persistently advertising Chrome right on the fucking google dot com main page (and YouTube and so on).
Perhaps they could care for the automation niche. There are thriving communities on macOS who are deeply into automation, and virtually no one uses Firefox. The ones who do stop because Firefox’s AppleScript support is non-existent, while Chromium’s (and thus every browser based on it) is top notch, even better than Safari’s.
I’m not talking developers, either. Non-coders frequently cobble up short AppleScript snippets do to what they want. When they visit the forums asking for help and how to do what they want in Firefox, they are directed to the open bug report which is old enough to drink.
I have seen plenty of users abandon Firefox on account of that gap. I tried to convey that to Firefox developers multiple times—both in person and online—and their response was to not care.
If they're relying on volunteers then they'd need a few folks with the right set of skills and a motivation to scratch that itch. I would personally love to see better AppleScript support in Firefox, but I won't judge anyone else for not stepping up if I don't have the inclination to either.
No we are talking about a non-profit and a for-profit at the same time, where the distinction is often not clear. But it is clear, that they included ads and "studies" by default in their browser, that did send data to whoever, without any user consent.
So no, I do not really trust them anymore. Still more than google maybe, but not enough to voluntarily send them my data. And this is a shame, because I would have liked to keep trusting them.
Telemetry includes personal information such as IP address and some people are (rightfully) concerned about it. Also we do not know for sure what is done with this data, as Firefox server side code (the one that processes the telemetry) is not open source (and even if it was it would not be a guarantee).
> Okay, did you enable the telemetry that lets them know you use it?
There would be no problem if Firefox shipped as a zero-telemetry browser, and all telemetry was opt-in. This would remove all doubt and if you want to send Firefox data you can choose to do so.
However that is not the case. Significant amount of telemetry is enabled by default. Choosing to go for opt-out vs opt-in is what is hurting Mozilla's credibility here.
What then happens (and I am speculating here) is that this behavior triggers most power users in a negative way (for various reasons, one of them being simply using your bandwidth and resources for telemetry and noone likes having a slower browser) so they do their best to disable it. This in turn leaves Mozilla with data that does not include most of its power user base, the one that actually has most impact on Firefox market share (because as 'techies' they install the browser for their family and friends). The crippled data leads to crippled product decisions, which in turn makes power users even angrier and thus we witness the death spiral of user attrition that Firefox is currently in.
Source? I don't see any IP address in about:telemetry window.
I would much rather lose a feature I use daily than send telemetry data.
Part of the old tradeoff was that extension writers could do almost anything to make the web browser do almost anything. Nowadays, extensions are much less flexible. I think for good reason: being able to click a few buttons and get pwned isn't really a desirable feature. But the tradeoff has moved. I don't think that's really an argument against Firefox, but consider that powerusers are often very conservative, I'm not surprised that it caused some disagreement.
The only thing I know of that's similar to that is how Mozilla has Google Analytics on some pages as part of the Firefox interface, but there they have a contract restricting how the data is used: https://bugzilla.mozilla.org/show_bug.cgi?id=697436#c14
(Disclosure: I work for Google, speaking only for myself)
This is simply not so. Google pays to be the default search engine on Firefox because it is beneficial for them. Had they not, this place would be bought out by Bing or whoever else, and in the end Google will lose more.
The funny thing about this is that it's a narrative, but is it correct? Configuration options may be low, but Chrome has added things like tab groups and a reading list / bookmarks sidebar. They're in no way aiming to be as customizable as Vivaldi/presto!Opera/xulExtensions!Firefox, but even stock Chrome is actually adding useful features, while most news I've seen from Firefox have been them removing unique features I've used and loved, like being able to sync keyword searches via bookmarks.
The only significant feature I've seen them add - and it's a doozy, I admit - is Containers. But that's cold comfort when other features get removed at a steady rate.
> It seems that the market niche of tech-capable people who value privacy and customisation over a simplified UX is not capable of sustaining Firefox on its own.
This may be true, but it can really come down to quality of product: Firefox is losing ground, but Brave for example is growing, and doing it by a privacy sales pitch (with some dumbfucks who think they're going to get rich off BAT added in - it's a cut from Brave's ad revenue, ffs, and individual ad viewers aren't worth shit except en masse when the money pools up at creators' and ad agencies' wallets).
> Okay, did you enable the telemetry that lets them know you use it? Receiving and analysing user data is increasingly important to delivering a good user experience. If open-source projects can't access the same data as proprietary ones do, we can't expect them to be able to react to user demands in the same way, and so we can't expect them to be able to compete in today's market.
This is true, but making decisions purely off telemetry stats and setting up self-fulfilling prophecies of making features harder to find and then saying nobody uses them isn't exactly the way either. Telemetry is a good jumping off point, I think, but as a sole director it's shit precisely because privacy-conscious users are going to turn that shit off if they can out of habit.
> I've never quite understood why Mozilla got such a hard time from users about telemetry.
I think a lot of the Mozilla userbase is from an earlier age, before everything became cloud-based subscription services. They long for the days of locally installable software, buying new versions vs. subscribing to an app, etc. Some are the kind of obstinate FOSS purists who'd use gNewSense even if it meant they had to use their computer as a command line only device.
Think about Pocket, for example. I was one of the abovementioned people and hated its inclusion, and people still grumble about it in part due to the source code, in part just due to the old bad blood.
They'd essentially need a relaunch with a new take and attitude - look at Brave, whose pitch is pretty similar, and how people are a-ok with monetized services within the browser so long as they're opt-in. The product's newer, and so the attitude people come to it is newer. And it's growing.
Finally, there's an issue of focus: The organization increasingly feels like general activists first, custodians of a product second, which is not a vibe much of the competition gives off. Actors like Brave and Vivaldi have firm, in some sense political stances, but they're of a narrower sort of user control and privacy. I know people at both orgs who do/have shown their politics, but it doesn't show at the org/product level. The user? Does. I never, ever want to hear shit like "we need more than deplatforming" from an ostensibly privacy and user centered organization.
Firefox or the (quite lost) Mozilla Corp ? They're not the same.
I've been building a browser full time the past year+ (synth.app) and FF core wasn't really even an option. They've done very little to make the engine usable outside of Firefox.
Now I'm sure there are a variety of savory and unsavory things that led here, but building that stuff out seems like a good way to grow the ecosystem. At least they would've had a chance at capturing the Brave/Opera/Edge/etc market and those seats at the committees.
This isn't to say that I'm not worried about these standards merging like this. I've spent many hours working out weird chromium only behaviors that websites rely on these days to do things (and egregiously so if they detect an agent remotely resembling chrome).
Enough features to distinguish on, enough political/managerial reasons for choosing an independent FLOSS engine over one controlled by Google.
Sure, Edge/MS won't move to this engine anywhere soon. Nor will Brave switch over tomorrow, or electron rebuild around their tooling. But the world is full or "HTML-2-PDF renderers, headless testing toolkits, (embedded) webview-libraries or electron-alike toolkits, which are now almost all exclusively Chromium based.
A lot of GUI based programs should think of implementing parts of it as a library others can use. I remember early Git implementations in IDEs where they just ran git commands in the background and parsed the command line output. Imagine if the same had been done with SQLite, would it still be as popular today?
I don't have much experience with creating desktop software, but it seems to me that separating the GUI from the "engine" would bring other benefits too.
I have often looked at OSS and wanted to use parts of it myself. An email client might have a really good mail parser that handles encoding, attachments etc. But decoupling it from the rest of the program would take too much time.
This sounds like the IE6 disaster all over again.
The gnarliness spans the whole stack. From weird java-applet like API escalation behavior if chrome is detected (e.g. Google properties feature gate a ton around this) to how there is not even a clear way to get a DRM license for a custom browser without waiting for Google indefinitely [1].
Here's a challenge: fire up a chromium fork and get it to run a relaxed DRM website like Netflix. If you get that far now try loading HBOMax with their fingerprinting/DRM protection on top. I'm not even sure it'd be possible in FF (at least without some DRM piggy backing if there isn't one).
[1] https://blog.samuelmaddock.com/posts/google-widevine-blocked...
Say hello to https://servo.org/.
Not the most appealing idea, but an interesting one. Might help move more people to essentially using Firefox.
This reminds that Wine uses Mozilla code for their Internet Explorer replacement (wine-gecko). I wonder how far behind Firefox's rendering engine that code is, and how much effort is involved for the Wine maintainers.
https://wiki.winehq.org/Gecko
Then I looked closer look at the history of Chromium and Blink.
The reality is that a lot of the other "Chromium-based" browsers actually only use the Blink renderer. They don't use many (if any) other Chromium components other than probably V8.
In ancient times, Blink itself was a fork of Webkit. So, does that mean Apple controls everything?? But Webkit actually came from KDE's KHTML, didn't it.. Linux wins...
The kicker for me is: Blink and V8 are open source, and anyone can fork them at any time. Because of this, Microsoft, Oracle, Brave - every "Chromium" based browser vendor is contributing code. So does Google really control us that much? Blink and V8 make a rock solid browser core and are being worked on by a lot of companies, not just Google. It's like the Linux kernel - kind of a marvel of open source. Not something we need to fight against so viciously, in my opinion.
(Edit: "rock solid" might sound extreme to some... The HTML and JS specs are absurdly complex to the point where there's basically no hope of anyone implementing them from 0. There's a lot of bloat in modern web, no doubt. But if you're really worried about crazy JS features cluttering your browsing experience, you can go clone the Chromium source and pull out the crap you don't like.)
Yes. Contributing code to something doesn't mean that you suddenly control the direction of that thing. Google still makes the big decisions about what gets to enter the codebase: which web features to support, which ones to deprecate, how to interpret standards, and how to slowly align the web with their own financial incentives.
I think the idea of gp's point about others forking code means the forkers can also influence the code because they control the fork.
Otherwise, if we take your comment at face value, we'd conclude that Google's contributions to Webkit means it can't "suddenly control the direction" of Apple's Webkit. That's true, but also becomes irrelevant because Google controls its fork of "Blink".
In other words, does Apple's Webkit control us that much? No, because it seems like Google's Blink/Chromium is sufficiently independent. If we go back farther in the timeline, are we concerned that KHTML controls us? No, because it seems like Apple's fork of Webkit is independent and not beholden to KHTML decisions.
If Microsoft really wanted to, it seems like they have the resources to do what Apple did to KHTML and what Chrome did to Webkit.
That's actually being done in the Serenity OS project! HTML renderer, JS interpreter, and Web Browser, from scratch:
https://github.com/SerenityOS/serenity
https://www.youtube.com/playlist?list=PLMOpZvQB55beChggmvk-s...
https://www.youtube.com/playlist?list=PLMOpZvQB55be0Nfytz9q2...
The end users don't care about who controls what. They care about having a simple, fast browser who just works.
In fact, what's often forgotten is that even before MS's illegal monopolization, IE dominated Netscape because it was genuinely better.
But a few short years later it was regular end users who were suffering due to IE and it's lack of competition, which led to MS sleeping on it and letting security issues (both technical and social) pile up.
On the other hand, much bigger problems in the world, so we go build something else instead of reinventing what Google has already built.
and almost all of Webkit has been rewritten from the time of the fork from khtml.
[1]: https://wiki.qt.io/QtWebEngine
[2]: https://www.falkon.org/about/
Let's say Firefox is the most advanced browser of the universe. How can you get people to install Firefox?
Chrome has the advantage here because it is preinstalled in every Android phone and Android has more than 90% market share.
The second advantage Chrome has is that it cannot be uninstalled from Android. The fact that Android phones have a limited storage space is a compelling reason to not install a second browser.
The third advantage Chrome has is the fact that more than 90% of people use Google has search engine and every time you access google.com with a browser other than Chrome you get a "Switch to Chrome" notification telling you that Chrome will help you "hide" annoying ads (without telling you that Google is responsible for the annoying ads) and you will be safe against malware. The regular user fears malwares and viruses more than ads or anything else because they think their bank account info will be stolen, so better security is a compelling reason to install Chrome.
Please, tell me, how do Firefox or any other browser can compete with the fact that Google is abusing their dominance of the search engine market and the mobile phone market to "force" people to use Chrome?
Together with Chrome, they ended up beating IE, at the time neither had a significant advantage in distribution, at least compared to IE.
So in theory, Chrome can be beaten, except that unlike IE, Chrome doesn't suck, in fact, about the only thing going for Firefox is that it is not Chrome.
Both are better than Safari on iOS though, which does force you to use it.
Somehow even with Microsoft promoting IE on their platform, people still chose to install an alternative.
https://www.kaiostech.com/company/our-story/
They claim that they are on 160 million devices.
And based on this:
https://data.firefox.com/dashboard/user-activity
Firefox has about 220 million users at the moment.
So, I wouldn't say that FirefoxOS failed, it just failed in their hand.
> For me Firefox is the only alternative to a complete Chrome hegemony in the sense that:
> it’s open-source in the real sense (a project that’s truly community-driven)
I missed when the community wanted to do away with tab groups, compact mode, or keyword searches synced via bookmarks. The project is handled by a corporation with a multimillion dollar advertising deal with one of the EvilCorps. Uhh, yeah.
> it has a great track record of fighting for its users and for a better Internet.
Last I checked, it's owned by a foundation that's very okay with advocating that others tell me what I should see on the 'net. "We need more than deplatforming" are not words I ever want to hear from a privacy organization's mouth. That and "fighting for its users" don't exactly go together, unless you believe the Foundation's purpose is to be its users' moral custodian in matters that are not tech-related.
The whole sales pitch of this thing is "you should use a browser that increasingly sucks, that's increasingly lacking in support, whose stewards get their money from EvilCorp and cheerfully advocate for Internet censorship, all because they use a different browser engine". When my option would be to use browsers that do not suck and actually improve release by release, have revenue streams not so beholden to EvilCorp and put their makers' personal politics aside for user control and privacy.
Choices, choices.
Ugh, I dislike the title of that post. I still claim that you're misinterpreting it, though. It should have been something like "We need better answers than deplatforming." Deplatforming is not the answer, and we need better ones.
Sometimes deplatforming is the right answer. Not when it's about a political agenda, but there are many many actually harmful uses out there, many of them illegal, and ignoring those on your platform is the same as facilitating them. But deplatforming is about as effective as sticking your finger in a dike for truly improving things.
In my opinion, Mozilla has done a decent job of being apolitical when possible. Yes, it does think you shouldn't see some things on the 'net, but those things are things like scams and malicious disinformation. It does not say that you should not see the latest blatherings of Trump or whoever, except perhaps when they're directly encouraging violence or sedition.
https://blog.mozilla.org/en/mozilla/we-need-more-than-deplat...
> Turn on by default the tools to [amplify factual voices](link points to below) over disinformation.
Their idea of "factual voices"?
https://www.nytimes.com/2020/12/16/technology/facebook-rever...
> The change resulted in an increase in Facebook traffic for mainstream news publishers including CNN, NPR and The New York Times, while partisan sites like Breitbart and Occupy Democrats saw their numbers fall.
The entire post reeked of political tribalism in a way I don't like from people who make my tools. While seeing less Breitbart and Occupy Democrats might be welcome, Mozilla were completely fine with third parties boosting the visibility of openly partisan organizations who'll happily lie to my face. No, no thanks.
Hm? When were keyword searches or compact mode removed? I’m still using them in 94.0
Keyword removal totally dumbed down my browsing experience on mobile. I fear the moment the same will happen on the Desktop version.
Any entity participating in a democratic society should be allowed to voice their support for keeping said society healthy. Antivaxxers and "the vote was stolen!!!" putsch supporters are a direct threat towards society itself.
There are things in a society where standing "impartially" aside is taking a stand in itself - a stand on the side of those who want to destroy society.
~ Karl Popper, The Open Society and Its Enemies, 1945
What is your feeling towards the summer 2021 rioters? Are they a threat towards society?
>Google’s massive development resources and marketing machine. >Most people not thinking about the long-term ramifications of ending up in a market with a single vendor in it. >Firefox losing its status of a shiny new thing over the years. >Mozilla’s inability to capitalize on the popularity of Firefox in the past. I think almost all of their revenue came from a search deal with Google.
The true reasons Firefox lost market share are:
1. Firefox has become a mess
2. Mozilla is terribly mismanaged
To see Firefox thrive, we have to push towards management change while there's still something to be saved or by forking Firefox
I would say:
The true reasons Firefox lost market share is because we, developer & tech people started to install Chrome on family computers instead of Firefox because it was safer & faster (way way faster). And we never came back from it.
Performance is a feature.
When Chrome came out, it was way better. Now I don't really see big difference in performance, they have similar extensions, frequent updates, sync, etc.
I prefer Firefox but I don't really need to install it on family computers because whatever browser they use is probably good enough.
I'm not so certain those numbers compare with the 10s of millions of people(100s?) who's default browser was hijacked by nefarious bundles in every 3rd party installer under the sun back in the 2000s and early 2010s.. Those people knew no better and have been conditioned(or just don't care) to continue whatever gets them interneting.
Which comes down to the reasons I've already stated.
The marketing campaign for Chrome alone, if it is even possible to assign a dollar value to it, would have cost billions of dollars for anyone other than Google.
Unfortunately I don't think this will help. If their market share is already low, creating multiple forks makes it even harder for devs to target.
Simply look at desktop software support on Linux for an example of why this doesn't work.
The tight relationship between rendering engine and browser has been broken by Chrome and its “children” (and in some way also by Apples enforced usage of their WebKit implementation in ios). Mozilla need to follow suit in order to survive, rip that rendering engine out, build a new browser and a “browser toolkit” to let other people build their own.
Most of the negative feedback from users comes from two paths, changes that break add-ons, changes that remove customization. Either of those two effectively reduce the value proposition, so I think negative feedback is granted.
The problem most 'core' users have is this UX ethos that some how we are not having more MAUs because we fail to "make changes to compete with Chrome". This has penetrated the Firefox team and has lead to a copy cat of UX features from Chrome and a 'dummyfication' of UX.
The reason Firefox is unable to compete with Chrome or Edge is not because of missing features or performance. Both Firefox and Edge have million dollar advertisement and OEM agreements. Talk to anybody on the street and everyone and their dog will know Chrome, Firefox not so much. The average users will use whatever is pre-installed. They will not go out of their way because of Chrome-like features.
This causality that somehow Firefox is missing market share because of features or UX is flawed. Firefox is playing a Goliath and David game, with billion dollar revenue companies. Accepting and embracing it's niche nature is a necessary first step.
I think it’s the second part that is more important than my initial (potentially unfair) generalisation.
In order to fund further development of gecko it needs to become a competitor to WebKit/blink and grab that market share in this new world of many browser front ends that are cropping up. Explore new business models, for example sign revenue share agreements with new browser developers in exchange for supporting (or even helping with initial funding) their development.
I don't think this is true at all. Anecdotally, a lot of Firefox users have been very receptive towards recent changes. Quantum was a huge success and I know very few people that miss the old Firefox with all of its jank.
> Mozilla need to follow suit in order to survive, rip that rendering engine out, build a new browser and a “browser toolkit” to let other people build their own
This is precisely what Servo is: https://servo.org/. Mozilla know what they're doing.
Great example - because Mozilla binned Servo!
https://twitter.com/steveklabnik/status/1295771633320448001
Also they moved way to slowly with Servo, starting it as a research project was correct. But they should have gone all in on it years ago.
I know they have taken parts of it and folded them into Firefox, but it should have been the the other way round. Take the bits of Firefox they could and combine them into something new with Servo.
one vote for the old FF because tabKitv2 is unsurpassed
Exactly. I would really like to use something google-free, but the interface of Qutebrowser is too good, and Qutebrowser can't use Mozilla's rendering engine, even though the developers would like to.
I think the core goal is influence: The ability to meaningfully change the web ecosystem or counteract changes that would be harmful.
Of course market share is necessary for influence, but I don't think it's sufficient: If Firefox gained a larger market share but at the cost permanently catching up to Chrome, I don't think a lot would be won.
Mozilla brand has value in privacy, not browsers. It could start VPN, cloud services, remote backups, smart home, security cameras... Even Android phones with stamp from Mozilla would be great.
There are no money in browsers, it is basically a feed tube from big corporation to its drones. Mozilla should not sponsor large corporations.
Firefox in comparison feels like being in a grand old house that was built before plumbing and electricity. You can tell that it used to be beautiful and polished, but the luster has faded over time.
In fact, switching to Chrome is agonizing because I lose my adblocker.
How much of the users are actually technical?
The Firefox user share is frequently seen through the lens of technical features, however, I have the suspicion that the vast majority of the audience is regular users who have no idea of anything technical.
And it could have take succeeded before Electron arrived if Mozilla didn't decide to let the project die.