Only because of iOS, I assume. But it looks like Apple might be forced to open things up and allow other browsers to run on iOS. If that happened, I'd expect Safari to drop like a stone.
Crazy thing is that I know a few Linux users that would love to have safari on our Linux machines for syncing.
Firefox on iOS is a horrible experience. My desktop I have switched to Vivaldi so I can easily sync tabs between desktop and phone. I don’t love Vivaldi but the overall experience is superior to Firefox on both.
Would prefer safari on my Linux desktop and use it on my phone
And I hope Apple doesn't manipulate the "power usage" data that always claims Safari is the lowest-power best-battery-saver browser on their platform.
I run Safari on MacOS for only that reason, that it allegedly gives me an extra hour or so out of my laptop vs. Chrome or Firefox. Of course, I should actually benchmark myself and find out.
In my experience it depends somewhat on the sites/web apps one uses (some are not well optimized for WebKit), but Safari definitely tends to be easier on the battery. It seems to try harder to get to an idle state and keep CPU usage down where Chrome and Firefox are happy to keep the CPU spun up, perhaps due to a “speed and bells and whistles at all costs” mentality in development (traditionally browsers have been marketed on speed and features rather than efficiency).
What's "only" about it? Smartphones gave everybody convenient internet access and thus increased the customer/user base enormously for everybody who publishes online. It's perfectly natural that the frontrunner in smartphones will have a huge chunk of the browser market.
If iOS allowed other browsers on the device (and I mean allow other browsers to run their own engines and not have to use Safari's engine under the hood - be first class citizens, just like Safari) then I doubt Safari would have such high numbers.
Maybe, maybe not. But there's nothing "only" about creating a massively popular way to browse the web. That Safari chunk will still be an iOS chunk. Device matters much more than browser for making web interfaces.
Fixing weird bugs like not loading cookies for a ~minute whenever the app needs to launch (as opposed to restore from background) would be a win too [1]
I switched to Safari on iPhone because I was always logged out of stuff on first load, super annoying. I miss the syncing, but not that much.
No, that's not going to happen. Chrome replacing IE could happen only because of MSFT's strategical abandonment of their browser for sabotaging the web in favor of the Windows platform. Apple actually is well aware of this mistake and began to invest into Safari when it's clear that they cannot prevent 3rd party rendering engines forever.
Internet Explorer references are overall just stale. Most uses of the catchphrase "X is the new IE" are basically shorthand for "I personally don't like browser X".
I always get downvoted for that, so it seems that Firefox supporters are subjective about their beloved browser, … and it doesn’t matter anymore whether I phrase it properly, since it will be shunned anyway, preventing Mozilla from actually recognizing their culture problem…
But Firefox has ads. It also has a lot of obnoxious browsing-interrupting interceptions saying that they care about our privacy. Which isn’t possibly true, because they also encourage, sometimes in the same page, to create a Mozilla profile… which gives them all required information to track us better - no matter whether they do it, gaining the ability to do it is pretty much a blank card to the NSA.
So thanks NSA and their Mozilla front and their downvoters on HN, have a safe imaginary trip to privacy!
Do you think that Google (part of PRISM, remember?) protects your privacy better by automatically linking your browsing data with your Google profile if you ever have the idea of logging in on a Google website before tweaking the settings?
And as far as I know, Mozilla can't access the key that encrypt Firefox profiles (as long as your profile password is not 123456). Didn't check the source code, but I guess that if they weren't doing that for real, someone would have spotted it already.
I don’t think Google does it better. But switching from Chrome to Firefox makes much less sense if Mozilla still performs advertising. And, least be said, fires a CEO for having made a private political donation one day, so it is not politically agnostic either.
You are correct that Mozilla has implemented profile encryption and it is believable. However, NSA has backdoors at every level, so having an account online isn’t really a good practice.
That's one of the side effects of aging engineers out of the industry so quickly. We've lost so many of the engineers who just lived through a crippling browser monoculture not much more than ten years ago.
And you see this all over the place, like microservices (The Network is the Computer, SOA, WebServices), WebAssembly (TIMI, P-Code, JVM, MSIL, PNaCL,...).
Lots of stuff that keeps happening because newer folks just don't have any clue of what came before, or why that fence is in the middle of the field.
I want Firefox to not be on the brink. I have had no problems with it on Linux over the last few years since I switched from Chrome. I do not wish to touch Chrome with a ten-foot pole.
It slows down my whole system when it tries to load a page in first boot (but librewolf doesn’t for some reason) the HID and webgl/webgpu support is bad…
It’s just not a very good browser compared to chrome forks or webkit based ones.
Same. About the only thing that's stable on F37. Updates to the kernel and other things have been giving me headaches, but FF and Steam are still solid.
I was running Firefox in Wayland just fine with my AMD Radeon 6650 XT but recently switched to an Nvidia 4060 Ti (16GB) and suddenly I started having crashes. I don't blame Firefox for this since other applications started giving me issues too (e.g. Dolphin and Discord). I place the blame squarely on Nvidia.
Nvidia's drivers suck but if you want to do AI stuff their cards are basically the only option until Intel and AMD complete ramping up their support for AI stuff. I wouldn't be surprised if two years from now AMD takes the crown with Intel being a close second (providing the best bang-for-the-buck) but for that to happen AMD needs to focus more on making actual implementations faster (e.g. PyTorch) and not just making minor incremental improvements to ROCm (and also make it so you don't need to use `amdgpu-install` to use it!).
Huh... I've exclusively used Firefox on Wayland for a long time now due to good fractional scaling support (unlike Chrome which took ages to stop using x11 by default). I agree that the webgl/webgpu support is bad but haven't seen the whole-system slowdown.
I haven't used it super extensively with Wayland, but so far I've not experienced any crashes. To clarify, I've been using Firefox on Debian virtualized with QEMU on aarch64, and the compositor is Weston, so maybe there are quirks on other setups. Overall, it runs impressively.
I have been using Sway and Firefox for the last three years at least, and have never experienced crashes. Sway and Firefox as packaged by Debian Stable. I really wish people on HN threads complaining about Firefox bugs clearly stated 1) their environment, and 2) who packaged the Firefox, because those are what could make all the difference.
The bug depends on a few factors that aren't really packaging-specific.
A) the default socket buffer size B) the polling rate of your mouse C) whether there's anything on your system or in your firefox profile that can cause enough lag that the buffer overflows D) whether your compositor has any workarounds for that protocol limitation
Well, I suppose a packager could have disabled wayland in firefox...
I had the same after forcing Firefox to do hardware acceleration on my Nvidia GPU. Firefox wanted to disable it, but I wanted to use my GPU anyway. Perhaps try resetting the GPU acceleration configuration?
Firefox isn't as stable as I would like it to be, but it's much better than any Webkit alternative I can find on Linux.
Google finally beat my hands with a stick firmly enough to get me off Firefox.
It was youtube. Not the ads -- I pay for premium -- but the fact that on FF they added an artificial 5s page load delay on firefox plus a bug has lingered for months where it always loads the last video, so you have to load every video twice. 12s/video is too much delay.
Compromised morals? WTF is the CEO of the Mozilla Foundation doing to earn $7M per year in salary? What about the Mozilla Foundation forcing out Brandon Eich because of a personal donation he made to a cause they didn't like?
Morals my ass!
I stopped using Firefox the day they kicked Brandon out and here's the kicker: I don't agree with the cause Brandon supported but I agree his employment shouldn't be affected by donations he made to support a ballot issue.
So yeah, the Mozilla Foundation can go straight to hell with that shit.
What really moved me away from Firefox was using Brave search. I had been using DuckDuckGo since the Snowden leaks. When DuckDuckGo announced they would derank results if they thought it was Russian propaganda or disinformation, I moved to Brave search. A week or so later, I decided that Mozilla was too woke for my liking, and started using Brave's browser, too.
You seem to value integrity, are you aware that Brave browser replaced affiliate URLs with their own? So if you wanted to support someone and use their affiliate link they took the liberty to replace that. I wouldn't touch that spyware if I got paid.
Just to make sure I'm following along, we were talking about how youtube includes a delay of several seconds if it detects a certain ad blocking browser extension. Firefox has that browser extension, and therefore Mozilla is a "compromised organization."
You violated YouTube's T's & C's and you're complaining about Google putting you in timeout for doing so. You steal from YouTube's content creators yet present Mozilla as the good guys. Have I summed that up accurately?
Gecko being a mess for embedded use pre-dates the Eich affair and Baker's payday.
As for Mozilla being compromised - maybe, but it's still less compromised than advertisement companies, crypto companies, tax evaders, and their likes.
> Why do you support a crooked company like Google?
Get back with me when the Mozilla Foundation has done a fraction of what Google has done in furthering our knowledge of computer science. Other companies making significant contributions to our knowledge of computer science are AT&T, IBM, and Microsoft. Would you prefer them to Google?
Also, the Firefox against the world meme is juvenile.
Like I said, get back with me when the Mozilla Foundation has done a fraction of what Google has done in furthering our knowledge of computer science.
I would also consider which Big Tech company you're fighting. Last I looked, Google wasn't cited as the cause of a significant uptick in US teenagers committing suicide and being plagued with mental health issues. I could go on, but in the realm of Bad Actors in the land of Big Tech, Google is actually one of the least problematic entities.
Brendan Eich was not forced out. He made the donation, he couldn't stand the heat of defending it, he left.
Also, personal donations can make you unfit for some positions. Significant parts of the community felt his donation was not in line with the values they wanted to see represented. And since you didn't agree with them you decided to leave.
Don't know, the pro LGBT stance of Mozilla/ Mozilla Foundation was not new in 2014 I believe.
So not having leadership with opposing view does not seem strange to me; donation was done privately but it end-up being public enough. There's enough hypocrisy and pink-washing ...
Might at times be at the detriment of Firefox but it's not like there is any alternative imo. So I don´t mind, it's not like if they remove their LGBT manifesto they suddenly will become relevant again and people will start to care about privacy.
Might be that LGBT people care more about privacy and that this manifesto will help them stay relevant.
And it's not like 2% is not a lot of people, TOR browser is certainly even less and it does not change the fact that I believe it's an highly important piece of software.
Even besides the compromised morals, just the fact that they know and understand that Google is intentionally doing nefarious shit to make us switch to Chrome and they just went along with it.
I must just be a naturally defiant person, but in that situation, I would go far, FAR, out of my way to make sure I never let them "win" with that kind of bullshit tactic.
Hmm. Maybe I should try uBlock. I usually don't like adblockers -- both on principle, because I believe in paying for what I consume, and because they tend to subtly break a website and cause hours of headaches at least once a year -- but I don't like feeding the beast either. I'll look into this.
Adblockers are highly configurable, you can simply disable them selectively in cases where you want to “support” those that sell your data to the highest bidder, if that’s your jam..
Your former comment indicates that you care about page load times, in which case an adblocker will typically reduce both UI yank and certainly network usage, in case you’re constrained.
Last time an ad-blocker caused a multi-hour debugging debacle, that turned out to not be the case. It was preventing me from logging into my bank even when it was supposedly disabled.
I use Chrome for Google's sites (Gmail, Youtube, etc) and Firefox for everything else. On Chrome you can install Youtube as an "app". That makes it easy for me to keep YT up and running while using Firefox for general browsing. Definitely recommend trying this approach out!
The one thing I miss from Chrome is the `thisisunsafe` feature to ignore whatever misconfiguration the webpage you're trying to access uses.
Recently, one of the dev servers that I tried to access misconfigured HSTS, which made it really difficult for Firefox to access the web UI. I fired up chromium, simply typed the magic word, and accessed it no problem.
Of course, ideally, there'd be no misconfigurations, but sometimes, I just need to access whatever dev server and I don't want to waste time on learning how to disable that particular security feature in Firefox temporarily.
While not recommended, and I would run firefox developer edition for that, you can disable (make the value false) `security.ssl.enable_ocsp_stapling` in `about:config`. You will be able to view sites with invalid certs/config. But will still prompt you that that something is invalid, and you have the choice to proceed forward.
Again, I would not recommend doing that on vanilla Firefox, they have Firefox developer edition version for these reasons. And you can run both side by side.
That's exactly the problem though. I know it's somehow possible, but the fact that I have to search for what's the internal boolean name for whatever feature I want to disable is simply a bad dev UX.
If there's a Firefox developer edition (I had no idea), they should enable all "I want to continue anyways" buttons by default. I mean, it's a developer edition!
The biggest difference is a catch-all phrase vs feature-specific booleans. So rather than have one place for everything, you have multiple of booleans.
I agree that if there was at least one boolean to always show the "continue anyways" button, that'd be acceptable to me as well.
> That's exactly the problem though. I know it's somehow possible, but the fact that I have to search for what's the internal boolean name for whatever feature I want to disable is simply a bad dev UX.
I think as a developer, searching for things are just part of the job, so if you have a niche need to debug or work with sites with invalid certs/configs, then it is not that hard to look on how to allow that. Firefox's docs are one of the best docs you can read to be fair.
> If there's a Firefox developer edition (I had no idea), they should enable all "I want to continue anyways" buttons by default. I mean, it's a developer edition!
To be honest, I use developer edition as my main browser and my profile is optimized and highly customized, so I don't remember is that was the default, or I changed it at some time (I keep it true).
But for vanilla Firefox which most of the users or potential users are not developers, I think this is reasonable default.
Compared to typing a nonstandard string in a nonstandard place? Going to about:config where all the deep settings are and searching for "ocsp" is downright obvious.
Not really... I don't even remember `about:config`. I know of its existence, but is it `config`, `:config`, or `about`, or ...?
So what I do is, I google, right? First page that comes up references how to fix the problem on both Firefox and Chromium-based browsers.
So on Firefox, I have to type the config page, then search for ocsp, then disable it. Then, I can finally access the webpage, but of course, I should remember to re-enable it after I'm done on the misconfigured server.
On Chrome, I can fire up an incognito window, type a magic keyword, do what I need, close the incognito window and go back to default.
Honestly, the latter is a vastly better experience in my world (I do backend/integration dev, mostly Python nowadays, probably a FE engineer will not care either way).
It might be this, it might be that, it might be all sorts of things. The point is you have to know what it is for each scenario, then you have to know where to go change it, then you have to know what the variable name is. Or you can know "thisisunsafe" which, while not being something you'll find using the settings for your saturday reading material, is something easily found and universally applicable to all situations without simultaneously turning every other connection you make into a security risk.
It's a great hidden feature just like Firefox has shift+right click/double right click opening the native context. No amount of "well you can just put this in the console in these cases or this in the console in those cases" makes these kinds of features any less useful.
Is it? The default options are for default users. Default users are dumb. It sounds like you have a non-standard case and the capacity to know the difference between misconfiguration and actual threats. It also makes sense that you are able to turn off certain features for default users when you want to do non-standard (default) tasks.
This drives me up a wall. I know the site. I trust the site. Yes, they screwed up something with their configuration or it's just ancient. I STILL WANT TO GO THERE!
>Firefox peaked at 31.82% in November, 2009 — and then began its long slide in almost direct proportion to the rise of Chrome.
It will be a sad day when Firefox is truly dead. But what did Mozilla expect? They spent so much time and energy on activist bullshit that doesn't really matter for THE BROWSER.
Well, yes and no. It does matter because if they had spent that money and effort on the browser and made it possible to donate directly to the browser project then there is a fair chance that those numbers would be better.
Maybe it was never really about the browser, but the platform. Safari dominates all Apple devices. Imagine if all computing was truly open and we could run any app anywhere. Would Chrome have had a reason to exist to begin with, or would Firefox have become truly ubiquitous?
> Imagine if all computing was truly open and we could run any app anywhere.
This was accomplished in the 1990s by Bell Labs with Plan9 and later, at the application layer, with Inferno.
It was additionally accomplished in the 1990s at the application layer by Sun Microsystems with Java and its applets.
Frankly, the history of computing is littered with well-engineered solutions to this problem and many of its variants.
The fundamental issue here is that businesses are involved and giving a business a monopoly over something so fundamental is usually a bad idea. The WWW succeeded because it grew somewhat organically.
The financial statements are also currently on the front page. That's a nice hot take, but the number that really stands out is 25% of revenue on management, a full 50% of salaries.
I think there are plenty of decisions worth consideration, but this is nothing to do with why Firefox is declining. It's because if I buy an iPad it comes with Safari and doesn't really let me use anything else (only a skinned version of Safari). If I buy a PC it's Edge. If it's an Android device it's Chrome. A Mac? Safari. Firefox is the default nowhere, and in this world because Google has almost limitless marketing power and owns one of the world's most popular websites they can push Chrome to mean that on PCs and Macs there is a strong push for people to move from the defaults to Chrome.
Firefox works great for me. It's just incredibly hard to get anyone to use it.
Although it would be a shame to not have a company behind it, couldn't a derivative of Firefox continue to exist with community support? It's not like Firefox is so lacking today that a lot needs to be done to compete with Chrome. If I didn't update my Firefox installation for a year, I likely wouldn't notice or care. It's a really good browser no matter what other people say, IMO. Mozilla either giving up on Firefox or kicking the bucket might even be a good thing for the Firefox codebase because it could open up opportunities for new companies to own a derivative and work on it.
I’m pretty sure the billions of marketing budget (for a while there was a Chrome billboard on every other bus stop in my city), aggressively installing it as part of Windows freeware etc. has at least as much to do with its popularity.
Maybe Chrome got the first 10% of its user base on its merits (that’s how I installed it at least); the next 30% definitely include a lot of people that don’t know what a browser is and got it via some other deal.
What could get people to move to firefox? Is the only way really to have have your browser be popular is to have it either be installed by default, or being advertised on a page that people use daily? Would be crazy if facebook had a banner stating "switch to firefox now" suddenly
There is another way: make your browser THE browser for power users. Add crazy features that appeal to 0.1% of the userbase. Allow a free extension system that allows developers to come up with features you haven't even imagined and see what gets mindshare.
Once you have committed power users who love your product, they will be more than happy to evangelize it to everyone they know. While their friends may not use any of the advanced functionality, they'll still use it if it works okay for them and their friends insist on it.
Mozilla had something like this, and chose to throw it all away to make a browser for Idealized Grandma that more closely resembled Chrome - because Chrome was successful, so they figured they'd copy what they did. But while Chrome was a fine browser, and maybe even better than Firefox in some ways, what this mindset missed is that the main reason for Chrome's dominance was a) being shilled on all the largest web properties, even with popup bars, b) being installed as the default on Android and c), being bundled in installers. Also, if I remember rightly, an advertising campaign. Mozilla was not in a position to do any of this. They should have - and still could - stick to their strength.
Now the only reason to use Firefox is ideological (privacy) and habit. I still use it at home. But I don't bother installing it anywhere else anymore. What's the point?
For me it's the Firefox sync feature. I install Firefox everywhere so I can instantly be up and running anywhere with all the settings, bookmarks, open tabs, logins, and addons ready to go on any new computer. It's a huge convenience and time-saver.
This article is like 6 years too late. The drop has happened, there's not really anything to base an "continuing free-fall" on. Even the articles own data show that Firefox usage has flatlined.
I know. That doesn't change that there is no basis for claiming that there is a "continuing free-fall" for firafox usage. I might fall further, under 2%. But free-fall is misrepresenting the usage data.
But their chart shows Firefox reaching above 3% usage in the past 12 months. It’s pretty consistent in the past few years being above that government support cut off. And that’s really just support. If people follow web standards Firefox will continue work.
I mean it has been a steady decline but parent comment was suggesting that Firefox is probably near the floor of their market share.
Google cripples adblocker extensions because of high interest rate and investor unease over the stock. If FF's market share was 50%, they'd still try to cripple adblockers.
Once people start hitting two 30s unskippable ads on every song they want to listen to on YT, they'll start searching on how to fix that. FF could capitalize on this trend.
They know their average user in 2023 is not the type to be cognizant that they're even using a "web browser" when opening an app like Chrome. I think it's really up to geeks like we to install Firefox on our moms' computers and inform them on why they should try it. That's how I got my mom to try Firefox with ad blocking around 15 years ago; otherwise she either wouldn't have known about it or she might have thought ad blocking was something nefarious. We just can't act as if we build it then they will come.
I don't know if that's still true. I have no data, but just anecdotally, I'm pretty sure almost everyone knows what a web browser is and what an ad-blocker extension does nowadays.
My anecdata shows that Google's recent decisions on the direction of Chrome and changes at Youtube have technically savvy users abandoning Chrome for Firefox,
Yes, every day Google seems to be doing things to drive people away, but it's not really moving the kinds of numbers that are going to make a difference. Also, some of those users will move to Chromium-based alternatives like Brave and Vivaldi, which might blunt some of the worst abuses but doesn't help ecosystem on the whole if you want a browser engine to exist that isn't controlled by Apple and Google.
Alternately, the technically savvy users understand that allowing Google's control of Blink to replace open standards with whatever implementation details Google prefers is to be avoided at all costs.
Yes, which took years and years to resolve. And only because in the end developers refused to play along. If the people creating web sites decide collectively to support only open standards, then Google has less leverage. It kinda worked with Amp, so it's not impossible.
The US government's page it uses to track web browser usage uses an analytics engine made by a company that makes its own web browser? That sounds like a pretty big issue!
I would guess lots of people no longer have access to the log files -- because the cloud is somebody else's computer (GitHub pages, etc) or because you're web scale and run your web server in docker so log files are ephemeral or maybe you're web scale so the only logging is dumping status messages to a background screen session.
Per the article, this is irrelevant. The case being made is that the figure seen by the government falling under 2%, which it is getting close to, will trigger a chain-reaction of consequences that will dramatically hurt Firefox, and it's not clear if Mozilla, the organization, could weather that.
It doesn't particularly matter whether or not the figure is accurate in that context. Maybe that can be fixed easily by having Firefox contextually relax tracking a bit or by having the government change how they perform the tracking, but the status quo is not really sustainable. And that's really all the article is saying at the end of the day.
USDS aren’t idiots, and if they haven’t realised this yet then maybe this post will focus attention. They want to support every citizen it’s reasonable to support (or at least I did when I was working for GOV.UK) and dropping support from a lack of knowledge shouldn’t be on the agenda.
GOV.UK is dramatically more competent than USDS, are they not? I admit I'm not terribly familiar, but I wouldn't want to depend on the agency behind the Department of Education and VA websites for anything. I've seen the VA site, in particular, do serious harm to the people it's meant to serve.
the va site is vast, to say any one team created the VA site would not be even close to correct.
They did help change over the old va.gov to the new va.gov (which was built as vets.gov), which imo has been a huge improvement.
(There are still many, many problems with the VA and its website. Just saying that 1. the new va.gov is a big improvement and 2. the USDS is far from being a single point of responsibility for it, or even _the_ major point of responsibility)
USDS certainly does not. The guiding principle at the time from what I remembered is to try to set "some standard" for all federal government websites to strive to because there were none.
We also helped with design and infrastructure support for ssa.gov (launched earlier this year) with a contractor team to try to boil down 60,000 pages to ~30 pages that people tend to use.
// opinions of a former USDS, no longer with the team
Can you elaborate on what in particular on the VA site that causes serious harm to the people it's meant to serve? I'm happy to bring it to the team or if you don't feel comfortable with stating it here, please bring it up to the open source website for va.gov.
https://github.com/department-of-veterans-affairs/vets-websi...
Sure, but the government HAS to make that determination in a data-driven way. It cannot be based on anything subjective, for what should be obvious reasons.
On top of that, said lack of knowledge is a stated goal of all privacy-focused browsers. GA-blindness is an implementation detail of these policies. Any method the government could use to accurately track that information is effectively a bug in need of fixing from the POV of the browser's developers.
The most practical answer is, as was posted by someone else here, the government spec'ing to a standard instead of a set of browsers, which it really should be doing in the first place. The mere fact that the current setup means that the government accidentally makes and/or breaks winners in that space is justification enough.
Yeah, I think the root comment of this thread is talking out of his ass. Third-party trackers are not needed, and wouldn't make sense to use, to discern browser market share; browsers self-report their identity and operating system unless specifically configured not to. For example, my User-Agent string in my GET request to retrieve Hacker News is: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:120.0) Gecko/20100101 Firefox/120.0".
Except we should be pushing for the elimination of user agent strings, too. They just end up being used as a lazy way for lazy developers to not test for capabilities.
The most recent example I've run into is Snapchat's web client: It reject's Firefox purely by user agent string, but then works perfectly in Firefox if you just have your browser lie.
I strongly agree. I don't think a website is going to do anything with my user agent string that benefits me. I'd much prefer a web where websites can't do things outside of the standard. We ne er needed webmidi, but a company that makes a browser/is hybrid definitely wanted it.
Speaking of Google, won't this interfere with their "look we're not a monopoly" payments to Mozilla Corp?
There is no standard that you can use instead of a set of browsers. There is no way of making sure that a website works with a browser other then testing it with that browser. The reason people test with different browsers is not that they want to use non-standard features, it's that even standard features often do not work in certain browsers.
Sort of agreed as of today, but this is not something that we just have to accept, especially considering the government doesn't really have a need to make use of the full suite of tools provided by the various existing standards. There are safe subsets to be picked in 2023.
The government doesn't design roads to conform to the top brands of cars and trucks. It specs them to a standard and any manufacturer can have their product certified as compliant. This both protects the public and gives anyone an opportunity to provide products no matter how small their market share is. Doing it the other way around would be madness, and I don't see why the same principle shouldn't apply here.
> The reason people test with different browsers is not that they want to use non-standard features, it's that even standard features often do not work in certain browsers.
This is exactly why sites should be tested for their conformance with the standard rather than with specific browsers. Testing against specific browsers just encourages browser-makers to continue to avoid fixing their shit.
If you want to make money or reach constituents, this isn't actually a viable option for anyone.
When people complain that they can't submit their DMV forms (or whatever) and you say, "well we followed all the standards, go find another browser" and they say "which one" and you say "I don't know, we didn't test with any browsers, we just test against the standard" who do you think they'll blame?
Is it really a standard if no one implements it in a way that everyone agrees on?
Is it really a standard if the dominant vendor just ignores the standard and does what it wants because then it becomes the "actual standard" ?
As a (terrible) example, look at FIPS. The government has the power to mandate a standard that everyone needs to implement. If instead of "supporting specific browser vendors" they "support a specific standard" then all vendors have a target that works with an agreed upon common ground.
> Is it really a standard if no one implements it in a way that everyone agrees on?
Plenty of standards are guidelines. The point is the website’s purpose trumps dogmatic adherence to a standard. If the site works against standards but not in the browser, it’s a failure.
But we can still have websites that work against existing browsers while also being strictly conforming to the standard, surely?
Basically, no proprietary features whatsoever. No draft features. No optionally-supported standard features without a fallback that fully covers the same underlying use case.
Given the history of standardisation for promoting interoperability includes numerous success stories and a pattern of resistance fading over time I don't see why we should expect web standards to be any different. The level of functionality needed by a typical government site has worked close to 100% correctly in literally every major browser for literally decades.
Then perhaps we should look at how we ended up in this state of affairs where testing against the standard doesn't actually ensure that your website works in the most popular web browsers out there, and do something about it? Like, say, mandatory standard conformance testing for browsers with >X% market share?
They're the government. They can create a spec or standard for browsers to be able to use government supplied digital services. It's done all the time.
This would be beneficial guidance for browser developers, but also for anyone developing government sites. Saying "whatever chrome is doing is our standard" is a cop out.
Sure there is a standard, are you saying the w3 doesn't exist? The issue is that somehow people here are arguing that it is sufficient to test that you are adhering to a standard by only testing against chrome, edge and safari (two of which are the same engine).
If you want test that you are adhering to a standard (if there is no testsuite available) you need to test against more than 2 independent implementations.
Firefox is not IE8, which declared lot of CSS3 and HTML5 standards as "won't be supported" in 2009, paving the way for its own extinction.
USDS serves basic pages and applets which work fine on Firefox. It is only a handful of very complex web apps like Photopea where the developer will say "run this on Chrome for best results".
> Sure, but the government HAS to make that determination in a data-driven way.
They really should be hiring a pollster to ask people which browser they use. It might be a bit difficult for those who use the default, but it wouldn't be that difficult to ask a couple of followup questions (e.g. which device) to determine which default browser that is.
The 2% rule USDS use is taken directly from GDS (gov.uk), so that isn't what your old employer's policy is at all. They have to define reasonable, after all.
That part of the article was just wrong, to be fair (I used to be head of the front-end community at GDS and helped set things like browser support schedules). Our default approach was to add up all browser share (yes, based on GA, but this was a while ago) until we got to 99%, then removed the browsers that were left over. So typically we wouldn’t consider dropping a browser version until it was less than 0.4% usage. You can use a colleague’s client-side tool to test this approach: http://edds.github.io/browser-matrix/ (assuming it still works).
Per the article, this is irrelevant. The case being made is that the figure seen by the government falling under 2%, which it is getting close to
So, the default position of the government is, "If we can't surveil you, we can't help you?" (Or taken the other way, you want us to help you? Let us surveil you!) This seems to be how it works out in practice, just because of favorable economics in mass surveillance. Example: RFID and license plate readers for toll collection. Various registrations with government agencies are another example.
Well, if the world including whatever governments, institutions, groups, interests, companies, FOSS projects, OS distros, etc... all want to depend only on Chromium, then fine.
If Mozilla can't even play this card, then they should really just shut down.
Or, maybe, like Wikpedia, they should stop begging for more-more-more, and spend what they get wisely.
Not to mention, they could simply start bug bounties and/or crowdfunding for actual deliverables and/or services (ie. a security team).
And if all this fails, then it fails. Maybe we'll simply get a Firemium or Chromefox/fix whatever the name. A fork where adblock works.
I work in govt tech, we already internally do not care about FF support at all and only really look to chrome based browsers (chrome edge mostly) and safari. Many people don't even know what it is anymore, seems like time killed this browser too. Mozilla spending too much time/money and other crap over the years
What does a government site need that you can't do on firefox? Honestly this is disenfranchising, you should consider the ethics of what you are proscribing for the populace. I should have a right to choose a browser that respects my privacy from a PC.
It's clearly not about what is needed, it's about what is tested. And spending resources on a browser that appears to have 2% of the market is not going to be a high priority.
Exactly. There are a plethora of browsers out there, and no one can be expected to test against all of them. As long as we go for a "government conforming to industry" mentality, then the cutoff has to be somewhere, and if Firefox doesn't make that cutoff, then that's all there is to it.
No browser deserves special treatment here. And this is as true for Firefox as it is for Lynx.
A long time ago we had something called "standards" that were intended to solve this problem. The idea was that developers of different browsers would get together in a neutral forum and agree common ground that everyone would support. That way developers could reliably build upon that common ground and expect their products to operate correctly in any browser. It was an excellent idea that heralded the success of the modern WWW.
Naturally this enforced competition wasn't in Google's interests as its browser became dominant and it adopted the infamous Microsoft strategy to deal with the threat. Apparently we're fast approaching the extinguish phase.
The correct solution to this is for influential public bodies not to insist upon supporting any specific browser or browsers but instead to once again support open web standards and therefore free access to their information and services for all.
This is almost certainly in their own interests anyway. Google has a nasty habit of suddenly killing off its non-standardised extensions. Relying on functionality that other browsers don't necessarily support as well seems unwise.
Nonsense. Only completely trivial standards work without testing actually implementations against each other.
How do you think WiFi devices work together? Is it because WiFi is a standard? Not really - it's because WiFi vendors all test their chips against other WiFi chips on the market.
I've been the person doing that testing. Checking interoperability with a range of other devices is one way you can look for problems but when it comes to signing things off the standard is the final word. Do you know what happens to the devices that don't comply with statutory radio transmission standards? They don't get sold.
Typically the cost of fixing the problem and going through the whole certification process again from the start is significant. There are some direct financial costs but mostly the damage is increased time to market. That's a great incentive for the maker to get their act together and comply with the standards like everyone else as quickly as possible. If you screw up too many times your product might be obsolete before you're ever allowed to sell it.
This, but for so many issues. Innovation is being stifled by platform monopolies. Standards can too but right now that’s not the primary cause. It’s a balance.
Completely disagree. Privacy is a 4th ammendment right, so the government has a duty to support privacy first browsers. How am I "secure in my ... papers and effects" if I must use a privacy destroying browser to interact with the Government? If anything, chrome support is what should be questionable.
Maybe you can make this argument - that the government should support technologies that emphasize privacy. That could possibly lead to some funding. Creating a policy to support a single vendor, however, is something that I think would be a bit odd for the government. Government spending is supposed to be devoid of bias where possible - you can't just give a contract to someone you like or think is cool, you need to show that it's in the taxpayer's interest (ie: they are cheaper, usually).
To say "we are going to support a browser with 2% market share because we like it more" would therefor be a really big deal. I think a far better avenue would be for the government to provide funding for privacy technologies directly, in an effort to increase their marketshare, and thereby making support of those technologies trivial to justify without any potential issues of bias.
The thing is, the government already does this. The majority of TOR's funding comes from the USG, for example. I'd suggest that maybe the government could fund Mozilla's non profit, to a degree.
This is all based on a premise that Mozilla is worthy of that funding. Is Mozilla really the privacy champion that it touts itself as? Would funding be contingent on anything else? If the government is so determined to prioritize privacy, why not Brave? Or some other entity? Or a new entity?
> The supreme court ruled there is no right to privacy in the same ruling that overturned roe v wade.
My understanding is that the consequence is denial of the right to privacy is limited to women while they are pregnant. Not a categorical denial of the right to privacy.
> The final decision was little changed from the leaked draft. Writing for the five-justice majority (with Chief Justice Roberts concurring only in the judgment), Justice Samuel Alito argued that the right to privacy is not specifically guaranteed anywhere in the Constitution. When unenumerated liberty rights exist — the right to raise your child as you see fit, for example — those rights must be “deeply rooted in the Nation’s history and tradition.” Reviewing the history of abortion restrictions in the early United States, Alito concluded that the right to abortion is not.
> The opinion ignited a firestorm of controversy. Predictably so: Dobbs is arguably the first case to formally rescind a fundamental constitutional right. The opinion also failed to explain how its logic would not also result in the overturning of Griswold’s right to contraception or a series of other cases that rely on the same logic as Roe. These include Lawrence v. Texas (2003), which invalidated laws criminalizing same-sex intimate sexual conduct, and Obergefell v. Hodges (2015), which recognized the right to marriage for same-sex couples.
Well, that’s what you get when you’re a Public Service. There’s an idiot living on the top of a mountain that needs some basic infrastructure? You got to get your truck out and build that supply line. You won’t do it? Then the government that granted you that Public Service status has renounced sovereignty on that part of the country
"appears to have 2%" is doing a lot of work he. If the earlier comments are accurate, the government stats are based on Google Analytics data that is specifically blocked or obscured by Firefox.
That 2% kind be breached, but the data doesn't accurately represent usage if Firefix is blocking GA in any meaningful numbers.
What's your proposal? Because taking an approach that isn't data driven means it needs to be a replacement, and you need to convince people that it's worth the risk of nepotism and bias.
For starters, how about not using a proprietary service from one of the biggest tech oligopolies which has strong economic incentives to misuse any data that passes through it? If government needs accurate tracking numbers to base its decisions on, it should roll its own tracking for those numbers.
My proposal was simply that data-driven decisions should be made based on accurate data.
Nepotism and bias aren't the alternative here. If you require that decisions are driven by data and you don't have access to accurate data, you should default to doing nothing. If anything, nepotism and bias sneak in when decisions are made despite the fact that no accurate data is avaliable.
so govt should spend tax payer money to support a browser by the numbers no one uses? for "virtue" ? going to have a hard time convincing people of that one
The problem Firefox has as far as I can tell is that the people in charge of the Mozilla organization would rather it be a social justice philanthropic foundation than a web browser and mail client maker and thus neglect their main product. And those they do have working on Firefox seem to want to remove features and play with UI.
For whatever the reason, Firefox does seem to enjoy playing with colors of the season more than trying to figure out where to take their rendering engine.
The thing that gets me about Mozilla is they were doing thing with xulrunner years ago that WebKit is being used for now with electron apps. But Mozilla didn't develop it. There were crossplatform apps being built with gecko.
I recall that Xulrunner, similar to the Firefox UI back in the day, hesitates just a little bit before responding to events. Perhaps xulrunner was too early in relations to computer performance back in the day, or they simply made a technical error when designing Gecko.
If that's the case there would be a sudden decrease in the market share graph around 2019 (although that graph is from Statscounter which has Firefox currently sitting at around 3.2%).
The decline has already been happening since around 2010 without any drastic ups or downs.
If this is the case, it seems that they need to recode the Enhanced Tracking Protection for GA to ensure that they get flagged as FFox.
Might also be useful to have a plug-in to make a daily 'ping'/check-in from FFox to any govt sites used by their users. E.g., I use USPS and SBA/SBIR sites, but only occasionally or monthly, but if most FFox users who did so got logged more like daily instead of ~fortnightly or ~monthly, it'd improve the numbers. (Obviously, also must be done carefully so as to not get wholesale discounted).
The cascade effect of the US Govt abandoning support would be catastrophic, likely terminal, which would be bad for everyone.
Do you have a source for a more accurate picture of Firefox' market share? Every single report I've seen shows the same thing: long downward trend and a tiny fraction of the usage of Chrome and Safari.
Yes I realized too late the term might be confusing. It's a radios streaming website/app, so not nerdy.
There is an Android app that uses a webview so that even favours Chrome. Also GoAccess doesn't unfortunately filter all scrappers/bots and most of them declare themselves as Chrome.
A sizeable part of the traffic is (non-app) Android and I don't think Firefox is huge there so maybe on desktop Firefox market-share is actually not as bad as we think?
“Enhanced Tracking Protection” is a poor name: it’s not just one thing, but has two modes: Standard and Strict. (There’s also Custom, which lets you go somewhere between the two, or restrict cookies even more tightly.)
The default is Standard. It doesn’t block GA. The cynic in me suggests they decided making Firefox disappear altogether from popular stats by default would have harmed them more than not doing it harms their users, or that the backlash would be too great for their liking.
Sources like Google Analytics and Statcounter are still chronically undercounting minority browsers and platforms, which are much more likely to block these sorts of things, and Firefox and Linux will be particularly heavily hit, but I’m sure the difference it makes isn’t as large as I’d like it to be.
What stood out to me was that they didn't break out mobile from PC. The mobile landscape dominates usage these days and extremely few people make an active choice in browser there. The presented stats to me reads more like Android vs iPhone than it does Chrome vs everyone else.
FirefoxOS was not stopped by Mozilla leadership due to a lack of hardware partners. The distribution model - mostly through carriers - failed because a key app was not available (WhatsApp) which caused a chicken and egg situation: no sales because no app, no official app because not enough users.
That's pretty interesting. I was around back then and hadn't recalled that there was such a lynchpin issue, but that makes a lot of sense as to why it suddenly hit such a hard stop. Were you able to support WhatsApp with KaiOS, or did the feature-phone target make it moot?
At the time, I had a FirefoxOS device made by ZTE in my hands.
It was so slow, it was unusable; even the first Android devices running on underpowered hardware were speed champions in comparison. Looking for an Whatsapp launcher was beyond the patience of even dedicated fans.
The rendering engine doesn't really matter - nothing is stopping Mozilla from implementing a better browser app than Safari.
Safari is _really_ good and a very high bar to catchup to, even if you don't have to implement the rendering engine and Mozilla is not exactly known for their friendly and refined UIs. Vivaldi on iOS is much younger by comparison and looks a lot better than Firefox.
I disagree. For the purposes of this conversation, I feel like it's the only thing that matters. The web doesn't benefit at all from a WebKit-based browser by Mozilla capturing some of the iOS marketshare. Websites will still have to cater to WebKit. Not Gecko or something new
> Mozilla is not exactly known for their friendly and refined UIs
I actually strongly prefer the Firefox app's UI to safari
> For the purposes of this conversation, I feel like it's the only thing that matters. The web doesn't benefit at all from a WebKit-based browser by Mozilla capturing some of the iOS marketshare.
I believe it matters because it shows Mozilla's ability to market their product (Firefox). If they continuously fail to capture user base on any platform, then what powers Firefox is of little consequence.
As an experiment, I just installed Firefox on iOS just to see what's up and honestly 4 screens of things to confirm before I even get to the browsing part? As a tech person I understood each of them of course, but no sane person would put 4 screens in a row blocking users from using an app they normally already know how top use. So no, I don't believe Mozilla has the required UI/UX skills.
Mobile browsers aren't sufficiently differentiated enough for a significant amount of people to bother changing the default. Does anyone really think Samsung Browser would get close to 1.6% if it were a free and unbiased choice?
Apple sets the rules, gets special access (new releases, features, platform changes, countless other things), and relentlessly captures their users into the Apple ecosystem/moat. You seem to think swapping the rendering engine is a trivial task but you're asking them to practically create a new browser. And for all that effort, you're still competing with an opponent that's basically cheating. I'm not sure why Firefox/iOS even exists, frankly.
It does, actually. For example, the reason why no other browser has the equivalent of Firefox containers is because they are the only ones with an architecture that allows for such isolation. Users of Vivaldi have been asking for containers for years now, and every time the dev team explains that they'd love to do it, but it can't be done without forking Blink and doing some massive surgery on it - at which point you again end up with your own thing, and have to play catch-up every time Google pushes yet another "standard" onto the web.
Just to add some anecdata, we have both Google Analytics (if you accept the GDPR tracking request…) and our own internal statistics based purely on useragents. Here are some percentages for November (this is Germany, generally far higher FF usage)
Ours:
Chrome 37.4%
Firefox 24.7%
Safari 21.1%
Edge 7.5%
Opera 2.6%
Also GA requires opt-in in the EU (even if some sites try to be clever and illegally make it harder to refuse than to accept) whereas presumably their first-party tracking is done in such a way consent is not necessary (e.g. sufficient anonymization that a data point can not be correlated with the user it originated from). Presumably FF users are more likely not to consent by default to begin with.
My programming blog (https://thecodist.com) sees Chrome 52%, Safari 27%, Firefox 9%, over six months covering a fair amount of the world. I use Plausible. I never found GA to be very reliable.
Do you anticipate the losses are due to people with aging machines upgrading and using a different browser? As a very happy Firefox user, I have a very hard time believing it's because people find the experience to be poor. I feel as if the losses you are describing have to be losses to defaults on new devices and people that fairly don't care enough to change them.
The desktop is virtually dead for any "normal" user, and their Android or Apple tablet/phone don't prompt them with a choice (other vendor constraints notwithstanding). It's not remotely a fair fight. You are guaranteed to lose users for reasons totally outside your control.
I think Firefox no longer has memory leaks.
I just which they'd follow Brave's BAT idea, or something along those lines.
Brave's BAT, while feeling kludgeful, is the only innovative idea in terms of funding sites nowadays.
Micropayments => dead
Coil => dead (sorry, on a open stewardship)
Flattr => unknown, guessing dead
So I want to block ads but I ain't depriving the websites of a way of earning money. If they want they can get my money -- but usually only that which was earned by wasting time to look at an ad.
I want there to be a proper micropayments system (hopefully something supporting fiat money instead of just cryptocurrency) but this functionality doesn't belong in the base browser, browser extensions are a much more appropriate place to put this functionality.
Unfortunately the Visa/MC duopoly isn't incentivized to create a micropayments system, so using a third party technology aka cryptocurrency seems to be the only way forwards for now.
Then you'll have to use Firefox because it's the only currently supporting extensions on mobile.
Still, I disagree. Extensions can be bought and sold. It's difficult to track those things.
I believe micropayments mechanisms should be integrated in the browser -- even if the provider can be changed.
Mozilla also just posted their State of Mozilla 2022 (this includes financial statements). From what I've read, it seems that expenses are up and revenue from search deals is down.
I think it's a pretty reasonable question when the salary is so incredibly out of line with what developers make. Is the CEO singlehandedly responsible for productivity equal to that of sixty or so developers?
You always have to /s here. I figure there are enough people reading HN who have different backgrounds in how they understand English that it's necessary.
Honestly yeah I had to read it a couple times, I didn't notice the joke right away, cause there are people out there who justify CEO salaries, I just can't remember the justification offhand.
Maybe if you'd referenced Chernobyl I would have picked it up sooner. Or THERAC, that's a classic.
Unfortunately, nowadays, unless you're among a group of people who already know your general opinions on things, it's nearly impossible to state an absurd position on some issue that a nontrivial number of people would actually, unironically, advocate for, until you get into the absolutely batshit stuff like "we should literally sacrifice poor people to the devil, then eat their flesh, to keep the rest of us from getting poor."
Carry on. I for one laughed at the obviousness of the iceberg jumping out. We definitely should be encouraging more careful reading than hinting and reading everything as if they are words only. Your comment is about as obvious as it gets. Unless... the icebergs are alive. But then we have a bigger problem. Global warming is their revenge!
> Salary has nothing to do with productivity at this level of an org.
That's nonsense. The difference at this level is you're not looking at personal productivity, you should be looking at a much broader interpretation. Except Mozilla doesn't. They've seen flailing commercial performance and have rewarded the CEO and laid off developers. It feels like madness because it is.
I love Firefox but Mozilla deserves to burn to the ground for this mismanagement.
It should always be personal productivity but as a CEO your productivity is how much better you're doing than someone else in that role would. In the modern world too often executive compensation is viewed as "How valuable is this company" instead of "How much is this particular executive adding to the value of this company" - that's why we're seeing it spiral into simply ludicrous numbers.
CEO salaries aren’t, and never have been, relative to the rank and file salaries.
The question is how much you need to be to get a competent executive relative to the open market.
You can argue whether they’re getting what they’re paying for but this doesn’t seem to be out of line relative to the leaders of other, similarly sized organizations. Also a non profit has to have higher salaries as there’s not a lot of room to offload that to bonuses or equity.
> The question is how much you need to be to get a competent executive relative to the open market.
No! The real question is what happens without an executive, but some cheaper leadership structure instead?
I mean, maybe a cheaper leadership structure (whatever it may be) would run the company into the ground, but, well, at least they would achieve the same outcome for cheaper.
Don’t know, as a shareholder I would be very happy with a capable CEO that is able to extract profits from a doomed product. As long as she’s bringing in more than she costs the ROI is positive.
the benchmark of what other CEOs make is a horrible metric. There is an entire industry of « Consultants » who will justify a higher CEO salary by claiming that other CEOs make the higher salary and then work with those other CEOs by point to your now higher salary.
Note, I didn’t say that it had to be relative to other CEO salaries. It has to be competitive to any other position that a candidate has available to them.
What would Mitchell make as an SVP at a FAANG company? What could they make as a startup founder?
True, Hiring a CEO is basically buying into an old boys network. It's like legalised corruption. With them you buy the goodwill of all of their buddies in other CEO positions.
However in this case it doesn't actually seem to be paying off.
This is true at most tech companies though - the CEO making a multiple of a typical dev salary. The large increases year over year, however, while Firefox loses market share, is a bigger red flag IMHO.
It’s simple math: how much revenue does she bring in, versus the costs. And how likely is it for the organization to find someone else that brings in equal or more, for reduced salary.
What a ridiculous analogy. What’s the iceberg here? Google Chrome? The originally underdog competitor they’ve known and battled for well over a decade?
Maybe this is sarcasm, but the chief captain of the Titanic (Edward Smith) was not responsible for the iceberg jumping at the boat but was responsible for steering the ship at high speed through water known to have icebergs. He even said in an interview that he could not "imagine any condition which would cause a ship to founder. Modern shipbuilding has gone beyond that".
No, the CEO(and board) are completely responsible. That is the point of leadership, to move the boat before it hits the iceburg or at least have a way of dealing with it.
Firefox is buggy but heavily advertised(or astroturfed, I dont know) on social media. Everyone knows about firefox, we don't need the ad. We need firefox not to suck.
Firefox being “heavily advertised (or astroturfed)” on social media isn’t something I personally have ever seen in the last decade. (Unless one includes Mastodon as social media, even though its userbase is nowhere near representative of the general public.) And today a substantial number of internet users are mainly using smartphones, and the default browser on that smartphone, and the very idea that one can use a different browser has faded from the culture compared to the early millennium.
The board of any startupy tech company focused on "innovation and changing the world" seem to be carbon copies of the fictional boards on the Silicon Valley satire show.
It's either that or they are referring to the board being useless against the CEO. Usually the board is the only group keeping a CEO in check. Honestly don't know from the tone of the comment though
No. Instead of being a board with a critical interest in Firefox, and who will continually challenge management to do what's best for FF, you've got a rubber stamp board who, let's be real, couldn't care less about FF.
The "planning" term should be read the same way as "estate planning" or "financial planning." They're a charity, so they have employees dedicated to ensuring a continuous stream of donations. For example, someone might pledge to give $X over the next 10 years, or to give a percentage of their estate to the foundation when they die.
This branch of the company is often called "development," but R&D organizations sometimes need to come up with different names because that term gets overloaded.
Interesting that only 1 out of 17 people in the senior management group is a technologist, and she's a senior director. No VPE, no CTO. Says a lot about the organization's priorities.
Despite all this nonsense about the board, Firefox remains the best browser in my experience. It isn’t cramming an AI chatbot and coupon codes during checkout into my browser experience or working to eliminate ad blocking.
They also don't ban and lie about anti-tracking extensions like AdNausium (a data poisoning adblocker[0]). Chrome banned it from their store. As well as other extensions like Bypass Paywalls Clean. Ultimately the Firefox addon ecosystem is simply freer
AdNauseum situation was funny, you had Firefox endorsing it as a high quality ad blocker in a Mozilla press release, then Google bans it because they consider it malware.
Folks have raised concerns about Mozilla's funding from Google Search, but it's pretty clear from their past actions that they see supporting ad blocking as non-negotiable. Their diverging implementation of Manifest v3, while still incomplete (it's rapidly improving in 120, most of the remaining issues are related to Fenix support and Chrome parity), is thoughtfully designed to continue to provide familiar APIs for ad blocking.
After Microsoft giving up on their rendering engine and joining the Chromium train I think the internet is in a perilous place. We're down to Blink, Gecko, and WebKit. Apple's monopoly on iOS browsers (soon to be undone) is unfortunately one of the last things keeping us from recreating the dark ages of IE's near monopoly on the market. I'd recommend at least supporting a non-Blink based browser like:
* Lunascape (actually has all 3 major engines built in. Great for web dev)
* Pale Moon - uses Goanna, a fork of Gecko
* Waterfox - focused on speed and privacy and compatible with Firefox addons
This sounds very much like cutting off your nose to spite your face.
The Mozilla board might be largely incompetent and/or corrupt, but they aren't actively trying to steal your data to profit from, and Firefox is still genuinely a less user-hostile product than Chrome.
I'm sadly almost in this camp. Firefox is incredibly important to me and is critical for the open web to survive.
Mozilla has proven to be really bad stewards, and as long as they exist nobody is going to pick up firefox. They've had many years to wake and up correct the course but choose not to, so it may be time to die. If Mozilla disappeared, a new organization could pick it up and run with it. If it weren't so overloaded in tech already, I might even call it "Phoenix" as it arose from the ashes of Firefox.
Since implementing EME, I'm not sure Firefox is critical for an open web, since by almost definition, EME isn't open. As a practical matter I can understand why they chose to implement it (though that was not without controversy), but let's not fool ourselves here.
that's an interesting point to consider. I wonder what would have happened had they not done it? Would it have accelerated the decline? Or would it have been enough to get services not to use DRM? I'm not sure, but I think FF may have just dropped to irrelevancy faster had they not done it.
I doubt this. Maintaining and developing a competitive browser is serious work, and needs skilled professionals working on it full time, as well as getting stuck in to the web standards process. That requires a level of funding that most community projects only dream of. I can't see any incentive for industry to put money behind it in the way that they do with Linux.
I have very few complaints about Firefox as software. I only wish more people would use it. (That includes you, dear reader!) It is actually great, and if you've ever complained about AMP, WEI or anything like that, using a non-Google derived browser is one of the few things you can actually do to reduce Google's power here.
Firefox are up against the power of OS defaults and dirty tricks in an age where most people don't really know what a web browser is. But if you have any awareness or concern about the health of the open web, you are absolutely educated enough to use Firefox. Of course there will be the odd minor workflow thing to get used to. But Firefox is great. All you really need is the motivation to choose something other than the default.
I feel like it's not that high for a CEO salary at a mature compnay. Staff-level engineers are routinely paid upwards of 1M these days (yay inflation). 6M for a CEO doesn't sound unreasonable.
If these numbers sound high ... $1M today was $500K in 1996.
> Staff-level engineers are routinely paid upwards of 1M these days
Yeah, at successful high performing trillion dolar tech companies like Nvidia or Apple, not broke*ss underperforming companies like Mozilla.
>6M for a CEO doesn't sound unreasonable.
It's unreasonable when you take into account Mozilla's lack of performance over the years. Where is their success, other than being kept on life support by being bankrolled by Google who's doing it solely to avoid anti-trust litigations over their monopoly on the browser market.
In a way, this is actually harming Firefox, knowing that they'll always be funded no matter how their product performs, just so that Alphabet has a legal David to their Goliath, gives them little incentive to try to be competitive.
The point is that less and less people use Firefox, so there seems to be a problem with success in that area, even if you are someone who still uses it (as am I).
Performance of Firefox has steadily gotten worse lately. My bank's website has massive lag when scrolling (1 second to redraw? Great!), but it works perfectly fine in Chrome. Firefox also gets into a state where screen updates in Streeview are laggy after anywhere from a few hours to a couple of days, but I can't figure out a way to predictably reproduce it on demand. Meanwhile, Chrome is snappy all the time. I also have to manually enable one of the acceleration settings under Linux. The end result is that I'm forced to use Chrome more and more as the Firefox user experience just plain sucks in these scenarios.
This is probably much more your bank's fault than it is FF. I think Mozilla has badly neglected FF to the point they probably deserve to die so a new org can take their place, but the blame for that most likely falls at the feet of the bank for not testing on FF.
These websites also keep adding bloat on top of bloat, hell, a goddamn button is 56 layers of nested divs these days instead of just styling the shit out of <button>.
Or they do some batshit insane "polyfill" nonsense that turns the <button> into 56 layers of nested divs behind the hood.
HTML hasn't caught up either, there's no <toggle_switch> that invokes the native toggle switch that every OS already has, devs are forced to mimic the toggle with 85 layers of nested divs.
Even if it were "not that high" for a CEO, what would justify a 7x increase while things have been looking downhill for years?
If anything, the board should have gotten rid of her at this point and hired someone else, even if at this higher salary it would make more sense than sticking with someone who obviously hasn't been leading the company to growth or sustainability (since they are trending downards).
> Genuine question. What is justifying Mozilla Corporation CEO Mitchell Baker's salary?
This question is why I don't expect Mozilla to last at its current course. I like their work, but the endless increases in CEO salary while their most important money maker is fledgling is not justifiable.
The increases look reasonable to me, but not when you consider their declining market share. I guess she only returned to the role of CEO in 2020, but she's been in leadership for a long time, and the org's performance has been poor.
In what world is DOUBLING one's salary within two years while the company overall and, most importantly, the company's absolute flagship product are in continuous decline "reasonable"?
>>On the same period, Firefox marketshare was down 85%. When asked about her salary she stated "I learned that my pay was about an 80% discount to market. Meaning that competitive roles elsewhere were paying about 5 times as much. That's too big a discount to ask people and their families to commit to."
So I bet it's something like:
Baker: "If you don't pay me market rates for comparable work, I'll leave and go mess up a different organization."
Google: "No, wait, stop, we'll get you the money!"
Considering all the unforced errors on Mozilla's part, I'm only half joking there (i.e. that Google is influencing the decision, via their search placement deals, to keep Firefox bad).
I expect it to last as a Zombie company in some sorts. Not a true, government subsidized zombie company, but a way for Google to pretend they don't decide the internet.
Google says 'Don't spend your money on bug fixes and you can get 400M for default search, and you get your 3M bonus.'
Oops, we arent allowed to speculate on HN? I'm just jaded...
So what do you care about more? Mozilla CEO making too much or Chrome getting to dictate the web?
Unfortunately there will always be things to complain about and no system is perfect. But we have to make choices like this and these are the results. You cannot complain about Google's control/dominance over the web and refuse to turn away from their products to use reasonable alternatives (when they exist). Firefox is by no means a bad browser and it is easy to switch over. You can also still use firefox and complain about Baker's salary but is this really a killer issue?
I want Firefox to continue existing and I want it to become a major player again. If not Firefox, maybe a newcomer, just anyone other than Apple and Google.
I use Firefox on every device and I recommend others to do the same. That doesn't mean I agree with Mozilla, though, and their misplacement of funds make me worry about the future of Mozilla and Firefox as a browser. After firing the Rust team working on Servo, you'd expect austerity measures across the board, as Servo was clearly too expensive to continue investing in, yet Mozilla saw fit to continue rising Baker's wages, despite having just laid off 25% of its workforce.
I wonder about how much longer Mozilla will be able to exist. It's oriented around activism first, Firefox second, yet most of its income comes from its browser, and only because Google is scared of being branded a monopoly. If any other platform rises to popularity (and there are a few rising browser engines in the works, mostly as hobbies, but still) and Google switches to funding that project rather than Mozilla, I don't see how Firefox can survive.
>Firefox's market share has been on the decline since 2010.
Its decline is also visible in Mozilla's own data [1], 252M users in January 2019 down to 188M in November 2023.
MAU has remained at around 188M since October, I would like to believe this is because of MV3 and the YouTube drama, but that would be naive.
Going forward I think there should be a position on the foundation [2] and corporation board [3] held by a community representative. At least then the community would have some say in the direction Mozilla is taking.
I did, went from working for a small non profit in the sustainable transport/urbanism sector to management in the telco industry. Sallary jumped almost 10x.
I can imagine that the CEO, or maybe a few other top officers, may say: "This is me who is bringing in all the search deals, which means all the money. Come on and try to oust me."
Mozilla is an open-source project. When an open-source project somehow loses its way, it's often forked by a new team of contributors who have a better idea. This happened several times: Open Office / Libre Office, MySQL / MariaDB, X86 / X11.org, hell, even GCC / egcs in the 1990s.
But this likely cannot happen to Mozilla, which is basically kept afloat by Google handing it some money for keeping it as a default search engine, about $400M a year currently [1]. There is little chance that an alternative "Better Mozilla" organization would collect as much, or at least half as much, to support a fork. It would e.g. take 33M users who agree to pay $5/mo for a Mozilla "support subscription" to collect $400M a year.
Maybe a web browser can be maintained for less than 400M, but likely not much less. The modern web is fiendishly complex, and you need both a desktop version (three platforms) and a mobile version.
> Perhaps ironically, this was also the genesis of Firefox
That's not entirely accurate (or at least, while accurate, is missing a lot of significant context) Mozilla was creating within Netscape, not in opposition to it, as a steward org for the open-sourcing of Navigator & Communicator. Even when Netscape was acquired by AOL, AOL continued to fund[0] Mozilla for years after the acquisition.
Firefox, however, was not. It was created because people didn't use most of the tools built into the Mozilla suite, and they were difficult to port (because they had a Motif frontend AND a GTK frontend).
That is the case, but even then Firefox really was a fork, within Mozilla.
Mozilla was created in 1998 to open-source Netscape Communicator suite. Mozilla released its own suite, also called "Mozilla" (e.g. "Mozilla 1.0" [0])
Independently of that effort, Dave Hyatt and Blake Ross made an experimenal, cut-down version of just the browser part of the suite, which they called "Phoenix", as in a Phoenix rising from the ashes. That's a fork. That's a fork by any metric.
They later rebranded Phoenix as Firefox, and eventually the Mozilla suite was abandoned. Mozilla changed tack in 2003 and switched to developing Firefox and Thunderbird as independent products [1]
Most people don't want to pay for anything. Look at all of the workarounds for news sites. I try to pay or donate for most of what I use but there seem to be a lot of people who want to get everything for free.
I totally won't mind paying for the occasional article I open, if micropayments were a thing! Pay a quarter, read something worthy.
The problem is that micropayments are not interesting for most news outlets: the friction of current solutions is high, the resulting revenue stream, unsteady. Monthly / yearly subscriptions bring a better revenue stream, and cost way less.
If micropayments were indeed zero-friction, and effectively zero-cost, maybe they'd be (reluctantly) integrated.
My experience w/ most news outlets is that they have a random article I'm linked to. That's not worth a subscription in my mind. A news service you have an ongoing relationship with is.
I'm deeply disturbed of this normalization of software as a subscription service. I want the return of good old days when people could pay once for their software and use it in perpetuity.
subscription is a significantly fairer revenue model for software which undergoes regular upgrades and has support, which is most software nowadays.
It makes sure that people who continue to use continue to pay. Upfront charges are often either too low with long term users free-riding or too high, in case the project is abandoned. Subscription makes it much more likely to price products correctly.
Leaving nonpaying users on old versions on browsers with security issues and who will no longer support the latest web standards will be bad for the web.
If users want to stay on an old version, why shouldn't they be allowed to? Sure, there may be additional security considerations or missing functionality, but there's nothing wrong with a user making that choice.
This model gets implemented, and then the comments section is littered with "I prefer when I didn't need to pay for software upgrades and backward compatibility!"
Yeah, people can get irrational about such things (like ignoring that they're only paying when they choose to rather than paying every month automatically).
But the solution to this is to offer both forms, as several companies do.
I hate the "subscriptionification" of everything as much as anybody, but there is a cost to ongoing updates to software. Especially on something like a browser, where both standards and exceptional behavior contrary to the standards change rapidly.
Maybe we could go back to where people paid once and could pay separately for support?
I remember the forced obsolescence. There were a few good software packages but many would frequently force you to upgrade from version 12.31 to 13.0 which isn't backward compatible i.e., "This software doesn't run on Windows XP"
At least with Microsoft, they are fanatics about backwards compatibility. It is pretty
rare for something designed for an OS prior to Windows XP
to not run on current Windows OS versions.
This is not a subscription to use the browser. You can always build it from source and use for free, as designed.
This is a commitment to support the development, because the development should be oingoing. Not Netflix-style, but Patreon-style.
(Also see how JetBrains handles "subscriptions" to their closed-source software. Once you've paid, the version is forever yours. Updates are bought with some additional sums if desired.)
Of all the types of software where you should be ok paying a subscription, browsers are the ones where should be most ok with it. Browsers, more than anything else, need constant updates because they're by far the biggest and juiciest attack surface for hackers, and also web devs will just stop supporting you if you're not on top of the treadmill of browser standard updates.
It's not feasible at all to call a browser "done" and leave it alone, so if you want one that's independent from adtech, a subscription is kind of your only option.
I, for one, won't trust a government to ensure my privacy.
The EU does better than the US for consumer-related privacy issues. But I don't think the same can be said when the government wants to slap a label of "national security" onto something. That puts us into a whole different world of "anything goes".
That would be a no from me. Considering the recent headlines from the EU wanting to scan every private message on the phones of it's citizens in order to "protect the children".
If not this time then the next. Just the fact that the commission was allowed to propose such a blatant privacy invading law is enough for me to know that privacy is not a something that the EU is serious about.
I don't think this is what being argued here. We know that privacy is an after thought of most companies even in the EU.
But to think that the EU would be the guarantor of everyone's privacy on the web, is completely ridiculous.
Also your argument is not valid. When Google detects that you break their rules they ban your account. When the government has this kind power, then they have the power to do worse things to you, like imprisonment, fines, putting you on a blacklist and much more...
While I have no idea about any of the aspects of Mitchell Baker's salary, I don't see this questioning of corporate CEO's. A generous reading might be that this is the salary required to avoid losing the CEO to some random VC selling useless widgets.
Looking at results since she got the job, maybe they should pay the money to such useless-widget company to poach her. I'm all for social enterprises but FF lost the plot.
They made a profit of roughly 150 Million dollars last year.
They have 1.2 Billion dollars in assets.
They have increased revenue from non-search deals significantly (56M -> 75M, up one third).
Despite all the gnashing of teeth in this comment section about woke Mozilla, they spent only 5 Million on grants last year. The vast majority goes towards developing Firefox and building up assets.
I had always just taken the statements that she is absurdly overpaid at face value and never looked into this myself. But Baker has overseen the rise of revenue and net income from almost zero to current numbers. If that doesn't look like a successfully run NGO, what does?
Not a big fan of CEO compensation in general, but I feel the one-sided focus on market share, which I feel is somewhat out of Mozillas control (can't even compete on the dominant mobile computing platform, anti-competitive Google leveraging its search monopoloy and advertising Chrome extremely aggresively, etc... ), while ignoring the actual financial health of the organisation is really biased.
If this was a for profit company I could agree with your focus on profit. Their mission statement is: "Mozilla is a global nonprofit dedicated to keeping the Internet a global public resource that is open and accessible to all.". You could argue the importance of market share at some percentages but below ~5% has to be considered a priority one emergency, if your goal is to keep the internet accessible for all. If their market share fell below 1% they would have effectively almost zero ability to steer standards.
> If this was a for profit company I could agree with your focus on profit.
There are two parts to Mozilla: a for-profit company and a non-profit company. They are separate. You are reading the mission statement of mozilla.org, not mozilla.com. Mitchell Baker is the CEO of the for-profit company, not the non-profit.
No. Mark Surman is the executive director of the non-profit (executive director is the term used for CEO at non-profits). She is the chair of the non-profit board, which is probably not a paid position (or paid very small token amount).
A non-profit company is not a zero-revenue company. It's a company that reinvests all profits into its designated cause. A non-profit org with a billion-dollar revenue is a great non-profit org as it can finance the work on its cause really well.
MAUs are down though and a non profit is supposed to be mission driven not revenue driven. The focus on market share is the belief that a better internet (Mozilla’s mission) starts by having a non profit browser leading the way. There might be some other metric but the financial health of Mozilla can only be one factor. Besides, at some point they get down to 0 market share and then the search deal revenue will go down (not sure again the next time they will be negotiating the deal)
i assume instead of google outright purchasing the company due to monopoly issues and internet outrage, they instead are just doing what they are doing now. thought i read they are up to 90% funded by google.. so its a little silly how these browser warriors champion their precious firefox or whatever other browser and condemn the evil chrome. but if you think about it they are all basically chrome developers. building ontop of chromium or working on firefox where those devs and chromes collab.
but in my opinion that isnt the reason google keeps firefox funded. i just think they do it for goodness sakes and not to cannibalize the only "competition". it really wasnt too long ago when it was chrome and firefox the two sleek awesome browsers saving the internet from nasty slow internet explorer.
So that means instead of investing money into making the browser better and clawing back some market share, Mozilla Corporation is sending money up to the owning Mozilla Foundation, in the form of profits, to spend on non-browser initiatives.
The only amount of money that can claw back market share is a number big enough to buy Google. Google controls the leading web properties and pushes its browsers through there.
That's absurd. Firefox has been at parity with Chrome for a long time, both are extremely mature technologies. Sometimes one is ahead of the other in one way or the other, but they are largely identical. The exception is when Google or Microsoft "accidentally" break their websites on Firefox.
It's pure fantasy to insist that the market share of Firefox is primarily driven by technical merit. Otherwise, you couldn't explain why Firefox is still at 20% in Germany, for example.
true. but it is much harder to switch between profiles in firefox, and containers don't really work for all the use cases you might want to use multiple profiles for (like, say having different bookmarks, and settings for different profiles).
Firefox also has containers which (AFAIK) Chrome lacks. The UI for Profiles is probably worse, but Containers dramatically reduced the need for them for many (but by no means all) use cases.
It's definitely not the case that Firefox is behind here. I would say they are slightly ahead overall, but which of the Browsers is ahead depends on your specific use case.
It should be fairly obvious that this has nothing to do with the reason that Chrome has 10 times more users.
I've tried containers, maybe something got better, but I just simple, one window with everything in my work profile, another window, everything in personal, it's so easy to use in chrome. I can close the work window at the end of the day, and open it again the next morning, carry on
> They have increased revenue from non-search deals significantly (56M -> 75M, up one third).
I'd love to feel optimistic about an increase in non-Google revenue, but 19M when the CEO alone is paying herself 7M of that alongside a 85M increase in expenses... it's still pretty hard to see it as a net positive here.
& of course the headline of this HN post is declining usage - that trumps profit either way imo
> What is justifying Mozilla Corporation CEO Mitchell Baker's salary?
The same thing that is justifying obscene salaries in general. A circle of greed where obscenely paid people decide what obscenely paid people should be paid.
I will say in their defense, they have a legitimate argument.
Offering a low-paying CEO role means you'll attract lower quality CEOs. The best CEOs have personal incentive to take the highest paying jobs. This element of competition does exist.
However, this ignores a few factors.
1. Mozilla don't seem to have a great CEO despite the pay.
2. Self-interest and CEO skills are not necessarily tightly coupled. They could be orthogonal. So a great CEO might be willing to take lower pay, especially a CEO that might be great for a company that is itself forgoing disgusting amounts of (ad) revenue in the interest of ethics.
3. (Not Mozilla specific but it's important to mention when this comes up) Decent regulations capping CEO pay would in fact remove this entire element of competition, freeing up companies from having to decide how much profit to sacrifice on the altar of business gods.
The relevant quote is "I learned that my pay was about an 80% discount to market. Meaning that competitive roles elsewhere were paying about 5 times as much. That's too big a discount to ask people and their families to commit to."
In other words, there's an assumption every corporation is required to have a CEO/Lawyer from the Technorati class who acts as a drain on the finances of the corporation, why should Mozilla be any different? Since the Mozilla Foundation is not a widely held corporation (and is a 501c3) there are only a few institutional directors ( from https://www.mozilla.org/en-US/about/leadership/#boards ): Baker (AOL), Chambers (McKinsey), Cooper (Walmart), Lakhani (MIT/Harvard), Lisbonne (Stanford GSB), Molotsi (Intuit) and Lund.
If you think Baker's pay should be cut, Lakhani is probably the person to talk to, he's chair of the compensation committee.
After watching VCs from the 70s to the current time (yes, I'm that old) I have a theory about tech startups. Their primary concern is to pump money from old school monied interests to old school monied interests' children. So if you have cash you want to give to your kids more or less tax free (or tax reduced), you send them to Stanford or MIT, then you arrange a meeting for them w/ your old school chum who's now a VC in San Jose or Palo Alto. You give the VC cash which is treated as an investment by the IRS, and then the VC gives the money to whatever bizarre tech startup is being run by their old school chum's kids. If you're lucky, you get a return on your investment and you pay whatever capital gains tax you need to pay (which is most often taxed at a rate considerably below that for earned income.) Your kids get a decent salary for a few years, and if they're lucky and smart, they git bought out by a big firm that makes them a VP or something. The VC should be lucky enough over time to make enough money on the 10% of deals that make it to acquisition to pay for the 90% that fail completely or get acquired on bad terms.
Mozilla always seemed to me to demonstrate this also works for non-profits.
Also... the story of "using money to transfer generational wealth in the upper class" is clearly not a universal. There are clearly startups that are innovative. They may be helmed by a handsome 20-something from Stanford, but that's just an historical accident. I am sure YOUR startup is in this category. But the "using VC investment as a money laundering scheme to evade generational tax" happens often enough my inner marxian shouts every time I drive down El Camino in Palo Alto.
And this part is purely opinion. I appreciate you probably have a different opinion and absolutely do not think less of you for having a unique perspective:
And besides, the goal of tech money is now just to keep the party going. The web is shit, intended to distribute content from major content producers or to be festooned with ads (twitch and youtube). iProducts are there to look sleek and provide just enough functionality to convince you to buy another iProduct. Though you're probably not in the target demographic anymore since China and India are at the beginning of the growth curve. Protocols and programs we used to use: SMTP/IMAP/eMail, (S)FTP/File Transfer, Veronica/Archie/WAIS/Search, etc. are pretty much dead or owned by Google, Microsoft or Yahoo's corpse.
I think the reason olds are nostalgic for Commo...
Is this bad for Google too? I thought Chrome needs Firefox to be somewhat successful so competition exists and the browser space doesn’t become a monopoly. Does the rising popularity of Safari and Edge negate this?
Mozilla has been a horrible steward for their project. They receive hundreds of millions of dollars a year and I have no idea where this money goes. It also doesn't help that their organization is full of purity testing and social activism nonsense that has nothing to do with making a good web browser. At this point I'm convinced that the reason that google is paying them so much is because they actually know that firefox is a failed project and keeping it alive as a zombie project actively protects them from anti-trust violations.
MS is investing hundreds of millions of dollars in Windows as well and yet I have no idea where that money goes. It's not like you can see all of the investments in mature products...
True. What are you going to do about it? I wish 1% of the effort denouncing FF because of the poor management were put towards forking it with better management.
A lot of people around me are switching back to firefox as chrome is showing signs of cracks, especially with the Youtube/ad-blocking saga on chrome.
Also, I don't think the US govt guidelines are going to have a dramatic worldwide impact on firefox numbers, the US is no longer the major online player it once was.
Yes, people that believe that Google will forever own the web are the same people that used to believe that Microsoft would forever own it. MS got arrogant and lost. Google looks like they are repeating that mistake.
A few things that could go against this:
- If enough people use Firefox, no commercial business in their right mind will tell these people to "please leave, we don't serve your kind". Seems to be true for obscure versions of internet explorer still in use. Definitely true for Firefox for some time to come.
- Legislation might force the market to open up on mobile. Right now Apple is blocking the Chrome and Firefox rendering engines (well they allow similarly named shells around safari). And Google of course "owns" the search and browsing experience on Android by default and twists every OEM into signing a restrictive licensing deal. At least you can install firefox on Android. There are some signs this might start changing. A lot of outrage around privacy and ad blockers might speed this up.
- People can still vote with their feet. If you watch Youtube on a laptop and you don't have an effective ad blocker, Firefox is blocking them very nicely. I watch a lot of youtube and 100% ad free, just saying.
> Yes, people that believe that Google will forever own the web are the same people that used to believe that Microsoft would forever own it. MS got arrogant and lost. Google looks like they are repeating that mistake.
I don't believe Google will forever own the web. But, like Microsoft did, I believe they will cause us a lot of pain before they're through.
I am afraid to say in my world if Google degrades Firefox for YouTube most people I know will switch to Chrome
I have had success persuading people to switch to FF (I am one of those people) but a degraded YouTube- even the outright criminality that involves - would be a deal breaker
The ad blocking blocking will work the other way.....
The government should really have a requirement to support at least one fully open option. I don’t care about the secondary effects; I’m happy not to use sites by lazy devs who can’t support two JavaScript engines. But there aren’t many alternative providers for government services.
Why is the US government even supporting specific browsers? It should support a standard like HTML 4 with no CSS or JS required. i.e. make the actual functionality on their sites simple to reduce the chance it doesn't work somewhere.
They're not Spotify. They're not trying to growth hack. They don't need to look pretty and have fancy animations and match some designer's dream down to the pixel. They can add CSS etc. to make things a bit nicer, but government sites should work with as simple of a browser as possible.
Highly regulated critical infrastructure like banks should be required to do this too.
> It should support a standard like HTML 4 with no CSS or JS required. i.e. make the actual functionality on their sites simple to reduce the chance it doesn't work somewhere.
You're right of course.
It's not really a case of 'supporting' browsers, it's a case of testing their sites against other browsers in case developers have accidentally written some non-portable Chrome only code.
This was very much the case in the IE6 era. Developers wrote and tested their sites for and with IE6, and were then surprised they rendered (in)correctly on Firefox and looked wrong. At least these days there are shim libraries, rather than having to explicitly rely on things like the box-model hack.
> Developers wrote and tested their sites for and with IE6, and were then surprised they rendered (in)correctly on Firefox and looked wrong
But that's the point: rendering shouldn't really matter. For things that are important like government systems, we should treat web "apps" much like TeX encourages: you specify the semantics, and let the rendering engine do what it will. Don't try to precisely control it. You can and should assume that users can totally override rendering with a custom agent, that browsers will disagree on default rendering, and that they may ignore your CSS instructions.
Like if someone wants to use a browser that always renders h1, h2, p, etc. with specific fonts and colors, totally ignores any CSS, and adds buttons to each table column header to sort on that column, that should all just work. Or if you want to use a braille output or screen reader.
For important tools and information, not entertainment/shopping, functionality should trump all other concerns.
My bank and now my power company have issues where I need to use chromium to fill out a form, and I don't understand it. I know Firefox supports forms. For whatever reason, javascript is loading the thing and screwing up somehow. I don't see why js is even involved, but frankly it screams incompetence to me. The easiest thing in the world to build, and they've broken it trying to make it look nice.
I don't go to my power company website for fun. I'm there to pay a bill. I need a form with 5 inputs and a submit button, and that's it. The rest of the screen can be plain white for all I care. Literally something I could put together in 2 minutes when I was 11, and it does not work. Paper should not have a better UI than a website.
Incidentally, this is why I'm not too worried about AI. If companies wanted cheap/easy/reliable systems, that's been doable on the web the whole time. People can't resist making things difficult for themselves, and they'll pay very good money to do it.
What compatibility? If Firefox breaks forms, then Firefox broke forms and needs to fix it. Not your bug. If Chrome renders differently from edge because they decided the default color on .gov sites will be pink on white and all padding will be multiplied by 1.5, then that's fine. Not a bug. Chrome just decided to present a different look.
If it's even possible for basic functionality to break in a way where you wouldn't obviously say the browser is broken, then you've built it wrong. That means you need to test that TLS/HTTP protocols are implemented correctly and that your documents conform to a schema.
> then Firefox broke forms and needs to fix it. Not your bug.
Not in the real world. In the real world, you've delivered a site that doesn't work and contractually, you can be sued or not paid for not fulfilling your contract.
That's the whole point of a standard (note that I said for .gov): the government says what standard they interop with. They either conform or don't. If other implementations don't conform, they are wrong. If the site doesn't conform, it is wrong. If it's not in scope for the standard (e.g. layout/font), it's out of scope. If the standard is underspecified or wrong somehow, you fix that and .gov now targets the new revision.
The government doesn't need to worry about market share. They can just dictate that this is what your browser needs to do to work with government systems. This is both more fair and easier for everyone; you don't have a moving target to aim for, and can just refer to the standard for what to do.
Governments exist to serve their citizens -- their users.
It's extremely user/citizen-hostile to say, "well our site works but no commercial browsers do, so I guess you can't register for a health plan this year over the web."
And I don't know about you, but I sure don't want the government building its own standards-based browser required for accessing government websites...
The government should set or adopt standards, not serve them. And they can and should provide a reference implementation.
We could easily and reliably do forms on mainframes. This is not complicated. And de facto, every browser supports HTML 4 forms anyway, so that's a non-concern.
They already set standards for things like needing to support TLS 1.3 with specific cipher suites. There's no reason they can't say HTML 4 forms and links are required for browsers to work on their sites.
No -- I don't want the US government (or any other) involved in setting web standards. The W3C is not going to be helped by being run by governments instead.
No -- I don't want the US government providing a reference implementation of web browsers.
No -- I don't want to log into a mainframe computer to fill out my taxes or sign up for Medicaid or a health plan.
The government should simply build services that work, in practical ways that are familiar and friendly to their citizens, according to the tools and habits their citizens are already accustomed to.
That means websites and apps for popular OS'es and browsers. It means phone numbers that work with existing telephones. It means offices in population centers.
Good governments come to where users/citizens already are. The shouldn't make users/citizens jump through hurdles to come to it, any more than necessary.
Like I said, the US government should just adopt the existing W3C standard.
It's crazy to me that 10 years ago people were against the standard for government documents being essentially "whatever Microsoft office does", but in 2023, we've decided it makes sense for the standard for government web sites to be "whatever Chrome and Safari do".
And as I've pointed out, for historical reasons, we already have an adequate standard that the major browsers already support. So just target that standard. It happens that this is also the cheapest, simplest, most reliable way to do things anyway.
But you're saying that the government should create websites according to those standards, and if it breaks in Chrome or Safari, the government shouldn't test and fix it. Rather, the browsers should fix it.
That's a position I just can't get behind. These are all just tools. The point isn't to follow some ideology, the point is to function.
And no, the government shouldn't formally "adopt" any specific W3C standard either, because standards evolve, and we don't want the government to get stuck in time. It should just write and maintain websites that work.
This isn't complicated. Businesses all seem to manage it just fine. The government doesn't need to do it any differently.
If a browser breaks forms somehow, then yeah I don't think it's reasonable for anyone to try to fix their website to somehow work (if it's even possible). Same as if they break links, or TLS, or HTTP. The government should just say "chrome 287 doesn't work".
The "evolving" standards of browsers mostly add a bunch of useless toys that create security vulnerabilities. There's no reason for serious sites to target them. The old standards do everything you need to quickly and easily make a functional tool that will require no maintenance for years or decades, which is exactly what you want from tools.
You are assuming that your developers were perfect and write sites exactly to the standard every time. In the real world they don't and XHTML lost, so all browsers tolerate and mask non-compliant pages to various degrees and in various ways, and will surface different bugs in your work. So it behooves you to test with the browsers your users are using to find those bugs before they do.
I am assuming that a professional can do their job, yes.
The whole XHTML thing where allegedly it never caught on because people can't write valid markup has never made sense to me. They're able to get typescript to compile now, right? If a dev couldn't write react code that compiles, we would fire them, right?
We have tools to check that your document parses and conforms a schema. We've had them for 20 years. It's easy enough to have that be part of your CI pipeline. The tooling is 1000x simpler than modern frameworks, and the thing that was allegedly difficult was that if you enabled conformance mode (which was opt-in based on DTD and/or MIME type), you had to open and close your tags instead of just opening them. Surely any middle schooler understands when you open a parenthesis, you need to close it?
I worked on fibre channel networks at IBM. They were all about high touch customer service, and had great data gathering and would debug issues that ultimately were caused by some other vendor breaking the standard. After proving we were doing the right thing, our answer would always be to tell the customer to turn off the broken feature on their other vendor's device (other vendors would do things like inject fake ACKs for large transfers to reduce latency ("acceleration"), which is kind of a no-no in reliable networks. We lowered latency in a standard compliant way by using multiple concurrent exchanges that we put together at the application level).
We did test with some other vendors, but IIRC only at a fairly basic level, and didn't support any of their non-standard behavior. We just used them to validate our own compliance to standards.
To clarify, I think it would be very bad if the government merely "targeted a standard" and did not test its websites on various browsers. I would consider it irresponsible professional behavior.
US government websites, as they exist, are often ancient, decrepit, and poorly funded. This will make them all worse and it will cost more. It will get in the way of people actually trying to interact with the government, and the leaders in the government will crap all over the project due to the angry calls they'll get from their constituents.
If we try to stick to pure ideals without any consideration for reality, reality will ignore us and move on. Or, to borrow an example from another field: in infosec, the most secure computer is the one that's never turned on.
They're not decrepit; they're unfashionable. Programs and websites that were somewhat decently written 20 years ago should and pretty much do run exactly the same today as they did then. It's not until "web 2.0" and SaaS that you find things that stop working after a few years/months.
That's exactly what you need for "poorly funded" sites, and I don't see why a site that's meant to be functional needs a Hollywood budget.
You're asking government websites to run differently from 99.9% of commercial websites out there.
First of all, that's just not going to happen for all sorts of practical reasons.
But secondly, you're totally ignoring UX and design. "Specifying semantics, and let the rendering engine do what it will" might work for developers who are used to interacting with API's. It will not work for regular users.
Regular users need to understand which button is the primary action. They need to understand which part of the content is the main body, versus a sidebar versus a header. They want columns that are correctly sized for their content. They don't want to have to scroll horizontally. They want responsive design that works on mobile too. They want something that looks trustworthy and familiar.
Websites are apps now. Asking to go back from presentation to semantics is like asking people to use the command line instead of GUI's. It's not going to happen, nor should it, because it's not user-friendly.
The only people it's friendly to are a niche set of developers with certain ideological beliefs that most web technologies shouldn't be used.
The things you describe aren't prevented by focusing on semantics, and are in fact enabled by it. Every modern app looks different for branding purposes, so users don't know what the buttons do. Things are complicated because we abandoned standard UIs that used to use the same widgets across every application.
And government stuff should work differently from 99.9% of commercial websites. Again, the goal should be for it to work. The government does not need to do marketing and make you feel like they are trustworthy. If you want to interact with social security, you go to ssa.gov. If you want to interact with the IRS, you go to irs.gov. End of story. They don't need to act like commercial entities because they do not have to worry about market share. Their share is always 100%. They need to just make their stuff reliably work, easy to figure out, and should make it cheap and easy to build. Basic HTML with minimal optional styles checks all of those boxes.
If you view the computer as a tool instead of a toy, you see that you really just need most websites to be a more convenient version of paper forms. It doesn't need to look fancy. It needs some boxes to type information, it needs to always work, and ideally every form on every website would stick to the same 5 or so types of input (rendered consistently by your OS) with no surprises. Government sites should take the tool approach. Commercial sites can sell toys.
Filling out your 1040 is "hard" because people don't understand what the words mean, there's a 100 page instruction manual that defines the terms, and it might require filling out other forms too (which you might just need to know somehow that you need to fill them out too). Other than that, the actual UI design is straightforward. You write/type numbers into numbered boxes, top to bottom, occasionally referring back to numbers you've already completed. You could progressively enhance with automatic calculations for relevant fields, but hand calculations work as a fallback.
Reliability is unrelated from UI, except insofar as simple UIs are easy to build, and therefore less likely to break. A paper form 1040 is perfectly reliable; it's not going to burst into flames when you're filling it out. As I said above, I couldn't even fill out my payment form on a modern site. It did not work at all. The form did not appear. That is not reliable. It also makes no sense if you know the page is ultimately using HTML, and that HTML has forms built directly in, and they always work fine.
And yeah, when I'm doing something like making a payment, setting up a transfer, doing my taxes, or even ordering a pizza, something like a slightly advanced paper form (e.g. with drop downs for options) would work great on my phone or desktop. Have a special request for your pizza that's not on the form? Put it in the free-form instructions box.
The "progress" we've made in the last few years is that I can't do bank transfers without switching browsers, which requires selecting a "to" account from a drop-down, a "from" account from a drop-down, and typing an amount. I don't see how something so basic can be so hard to do correctly. There's literally no need for any javascript at all. I don't see the usability gain from whatever they're doing.
Would an address lookup service be acceptable? One of those where you start typing your address into a box and it fills in all of the address fields based on which address you select.
If a new version of this is created, shouldn't it be tested on browsers? Which browsers should it be tested on?
Exactly this -- it's about testing and ensuring something works.
And no matter how "standardized" things get, there are always going to be implementation differences (whether due to mistakes or underspecified specs or partial implementation) and also just straight-up bugs between browsers.
At least these days there are shim libraries, rather than having to explicitly rely on things like the box-model hack.
Are people actually now using the older term, "shim," and not the newer "polyfill?" I was a grumpy old man when people started to tout the new terminology, when there were perfectly good terms already.
The main issue is every startup and small business ties themselves to the gsuite apps and ultimately falls down the path of using and then requiring gsuite auth and often chrome as a whole for all work browsing. It is quintessentially the new IE. almost all my browsing during the day has to be chrome whether I like it or not and that has been true at my last 4 organizations. Three of which are multi billion dollar companies and two with tens of thousands of employees
If your organization uses beyondcorp for zero trust among several other Google products, they only work in Chrome. Many MDM solutions also only do hardware verification through chrome during the auth loop for gsuite and not other browsers. My current organization blocks the installation of other browsers in their jamf configuration as well, so it wouldn’t matter even if beyondcorp did work in another browser
I'm not sure anymore that "The Web" is worth saving anymore. I find myself browsing less and less original content. The content that dominates is polarized between Internet Hate Machines on one extreme and Corporate Astroturfing on the other.
A lot of the interesting people I follow are already using Gemini (though I remain unconvinced that that's a way forward).
1. Firefox blocks various analytics and tracking quite aggressively by default. Additionally, users of Firefox are, by and large, privacy minded and will have further mitigations. Any count of Firefox users is likely to be undercounting.
2. For the kind of basic web stuff(simple pages, forms etc) that USWDS supports it shouldn't matter greatly if Firefox is not supported. Theses standards are mature and Firefox supports them well, most thing should just work. Now, if websites go out of their way to block Firefox users that's a different problem.
But i doubt that will drive the numbers.
On a side note, I think percentages will overstate firfox's decline. The number of devices with browsers per person will influence it heavily and that number is ever increasing.
I think the average person in my circle has more than 3 and many have more than 4 devices with they use to visit .gov sites (i.e. ipads, phones, laptops, but not including the fridge, car, tv, etc)
839 comments
[ 3.0 ms ] story [ 347 ms ] threadFirefox on iOS is a horrible experience. My desktop I have switched to Vivaldi so I can easily sync tabs between desktop and phone. I don’t love Vivaldi but the overall experience is superior to Firefox on both.
Would prefer safari on my Linux desktop and use it on my phone
And I hope Apple doesn't manipulate the "power usage" data that always claims Safari is the lowest-power best-battery-saver browser on their platform.
I run Safari on MacOS for only that reason, that it allegedly gives me an extra hour or so out of my laptop vs. Chrome or Firefox. Of course, I should actually benchmark myself and find out.
I switched to Safari on iPhone because I was always logged out of stuff on first load, super annoying. I miss the syncing, but not that much.
[1]: https://github.com/mozilla-mobile/firefox-ios/issues/11994
Chrome and Firefox are already on iOS – if they're allowed to swap out their rendering engine, is this something customers will actually care about?
But Firefox has ads. It also has a lot of obnoxious browsing-interrupting interceptions saying that they care about our privacy. Which isn’t possibly true, because they also encourage, sometimes in the same page, to create a Mozilla profile… which gives them all required information to track us better - no matter whether they do it, gaining the ability to do it is pretty much a blank card to the NSA.
So thanks NSA and their Mozilla front and their downvoters on HN, have a safe imaginary trip to privacy!
And as far as I know, Mozilla can't access the key that encrypt Firefox profiles (as long as your profile password is not 123456). Didn't check the source code, but I guess that if they weren't doing that for real, someone would have spotted it already.
You are correct that Mozilla has implemented profile encryption and it is believable. However, NSA has backdoors at every level, so having an account online isn’t really a good practice.
That's one of the side effects of aging engineers out of the industry so quickly. We've lost so many of the engineers who just lived through a crippling browser monoculture not much more than ten years ago.
Lots of stuff that keeps happening because newer folks just don't have any clue of what came before, or why that fence is in the middle of the field.
It slows down my whole system when it tries to load a page in first boot (but librewolf doesn’t for some reason) the HID and webgl/webgpu support is bad…
It’s just not a very good browser compared to chrome forks or webkit based ones.
Nvidia's drivers suck but if you want to do AI stuff their cards are basically the only option until Intel and AMD complete ramping up their support for AI stuff. I wouldn't be surprised if two years from now AMD takes the crown with Intel being a close second (providing the best bang-for-the-buck) but for that to happen AMD needs to focus more on making actual implementations faster (e.g. PyTorch) and not just making minor incremental improvements to ROCm (and also make it so you don't need to use `amdgpu-install` to use it!).
I am on X though, perhaps a Wayland related bug or config thing?
Have you tried:
- running with terminal to see errors
- running with a new profile
I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.
https://github.com/swaywm/sway/issues/7645
https://bugzilla.mozilla.org/show_bug.cgi?id=1743144
Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.
Well, I suppose a packager could have disabled wayland in firefox...
Firefox isn't as stable as I would like it to be, but it's much better than any Webkit alternative I can find on Linux.
It was youtube. Not the ads -- I pay for premium -- but the fact that on FF they added an artificial 5s page load delay on firefox plus a bug has lingered for months where it always loads the last video, so you have to load every video twice. 12s/video is too much delay.
Ah well, it was good while it lasted.
Morals my ass!
I stopped using Firefox the day they kicked Brandon out and here's the kicker: I don't agree with the cause Brandon supported but I agree his employment shouldn't be affected by donations he made to support a ballot issue.
So yeah, the Mozilla Foundation can go straight to hell with that shit.
Good riddance!
We all lose if it's only Chrome.
Also, anybody can use the Gecko web rendering engine, yet project after project after project has picked the WebKit or Blink rendering engines.
And no, I haven't "shot myself in the foot" - when I replaced Firefox I found two great browsers: Brave and Vivaldi.
The better question is why you continue to support a compromised organization?
As for Mozilla being compromised - maybe, but it's still less compromised than advertisement companies, crypto companies, tax evaders, and their likes.
And Brave and Vivaldi are based on Chromium, so they help Google that Chromium sets the standards for the web.
You already shot yourself, just didn't recognize yet.
Why do you support a crooked company like Google?
Get back with me when the Mozilla Foundation has done a fraction of what Google has done in furthering our knowledge of computer science. Other companies making significant contributions to our knowledge of computer science are AT&T, IBM, and Microsoft. Would you prefer them to Google?
Also, the Firefox against the world meme is juvenile.
>Get back with me when the Mozilla Foundation has done a fraction of what Google has done in furthering our knowledge of computer science.
https://developer.mozilla.org/en-US/
I would also consider which Big Tech company you're fighting. Last I looked, Google wasn't cited as the cause of a significant uptick in US teenagers committing suicide and being plagued with mental health issues. I could go on, but in the realm of Bad Actors in the land of Big Tech, Google is actually one of the least problematic entities.
Also, personal donations can make you unfit for some positions. Significant parts of the community felt his donation was not in line with the values they wanted to see represented. And since you didn't agree with them you decided to leave.
So not having leadership with opposing view does not seem strange to me; donation was done privately but it end-up being public enough. There's enough hypocrisy and pink-washing ...
If it's the former then what business do they have caring about Brandon Eich's personal donation to support a ballot initiative?
If it's the latter then it's a conflict of interest and Brandon Eich should be asked to leave.
Might at times be at the detriment of Firefox but it's not like there is any alternative imo. So I don´t mind, it's not like if they remove their LGBT manifesto they suddenly will become relevant again and people will start to care about privacy.
Might be that LGBT people care more about privacy and that this manifesto will help them stay relevant.
And it's not like 2% is not a lot of people, TOR browser is certainly even less and it does not change the fact that I believe it's an highly important piece of software.
I must just be a naturally defiant person, but in that situation, I would go far, FAR, out of my way to make sure I never let them "win" with that kind of bullshit tactic.
Your former comment indicates that you care about page load times, in which case an adblocker will typically reduce both UI yank and certainly network usage, in case you’re constrained.
Last time an ad-blocker caused a multi-hour debugging debacle, that turned out to not be the case. It was preventing me from logging into my bank even when it was supposedly disabled.
No surprise Google is doing those tactics if people react like you :( ...
Recently, one of the dev servers that I tried to access misconfigured HSTS, which made it really difficult for Firefox to access the web UI. I fired up chromium, simply typed the magic word, and accessed it no problem.
Of course, ideally, there'd be no misconfigurations, but sometimes, I just need to access whatever dev server and I don't want to waste time on learning how to disable that particular security feature in Firefox temporarily.
Again, I would not recommend doing that on vanilla Firefox, they have Firefox developer edition version for these reasons. And you can run both side by side.
If there's a Firefox developer edition (I had no idea), they should enable all "I want to continue anyways" buttons by default. I mean, it's a developer edition!
I would like a better way to bypass these TLS errors, but hidden booleans and secret phrases aren't that dissimilar.
I agree that if there was at least one boolean to always show the "continue anyways" button, that'd be acceptable to me as well.
I think as a developer, searching for things are just part of the job, so if you have a niche need to debug or work with sites with invalid certs/configs, then it is not that hard to look on how to allow that. Firefox's docs are one of the best docs you can read to be fair.
> If there's a Firefox developer edition (I had no idea), they should enable all "I want to continue anyways" buttons by default. I mean, it's a developer edition!
To be honest, I use developer edition as my main browser and my profile is optimized and highly customized, so I don't remember is that was the default, or I changed it at some time (I keep it true).
But for vanilla Firefox which most of the users or potential users are not developers, I think this is reasonable default.
So what I do is, I google, right? First page that comes up references how to fix the problem on both Firefox and Chromium-based browsers.
So on Firefox, I have to type the config page, then search for ocsp, then disable it. Then, I can finally access the webpage, but of course, I should remember to re-enable it after I'm done on the misconfigured server.
On Chrome, I can fire up an incognito window, type a magic keyword, do what I need, close the incognito window and go back to default.
Honestly, the latter is a vastly better experience in my world (I do backend/integration dev, mostly Python nowadays, probably a FE engineer will not care either way).
You can do the same on Firefox (at least developer edition). I thought that you want to do that without going to incognito mode.
It's a great hidden feature just like Firefox has shift+right click/double right click opening the native context. No amount of "well you can just put this in the console in these cases or this in the console in those cases" makes these kinds of features any less useful.
Is it? The default options are for default users. Default users are dumb. It sounds like you have a non-standard case and the capacity to know the difference between misconfiguration and actual threats. It also makes sense that you are able to turn off certain features for default users when you want to do non-standard (default) tasks.
edit: Well comment below me just mentioned a Firefox developer version, wasn't aware of that.
full-screen-api.ignore-widgets
which makes videos full screen to the browser size.
It will be a sad day when Firefox is truly dead. But what did Mozilla expect? They spent so much time and energy on activist bullshit that doesn't really matter for THE BROWSER.
This was accomplished in the 1990s by Bell Labs with Plan9 and later, at the application layer, with Inferno.
It was additionally accomplished in the 1990s at the application layer by Sun Microsystems with Java and its applets.
Frankly, the history of computing is littered with well-engineered solutions to this problem and many of its variants.
The fundamental issue here is that businesses are involved and giving a business a monopoly over something so fundamental is usually a bad idea. The WWW succeeded because it grew somewhat organically.
https://news.ycombinator.com/item?id=38530382
Firefox works great for me. It's just incredibly hard to get anyone to use it.
Nowadays KaiOS profits from it.
Hopefully the DMA can help? I’m not using Firefox on iOS mainly due to a lack of extension support.
Chrome got big bc it was radically different than IE and Firefox jumped on the lightweight trend far too late.
Maybe Chrome got the first 10% of its user base on its merits (that’s how I installed it at least); the next 30% definitely include a lot of people that don’t know what a browser is and got it via some other deal.
https://support.mozilla.org/en-US/kb/how-use-firefox-contain...
Once you have committed power users who love your product, they will be more than happy to evangelize it to everyone they know. While their friends may not use any of the advanced functionality, they'll still use it if it works okay for them and their friends insist on it.
Mozilla had something like this, and chose to throw it all away to make a browser for Idealized Grandma that more closely resembled Chrome - because Chrome was successful, so they figured they'd copy what they did. But while Chrome was a fine browser, and maybe even better than Firefox in some ways, what this mindset missed is that the main reason for Chrome's dominance was a) being shilled on all the largest web properties, even with popup bars, b) being installed as the default on Android and c), being bundled in installers. Also, if I remember rightly, an advertising campaign. Mozilla was not in a position to do any of this. They should have - and still could - stick to their strength.
Now the only reason to use Firefox is ideological (privacy) and habit. I still use it at home. But I don't bother installing it anywhere else anymore. What's the point?
Blocking ads in Android. That was my gateway into going back on all of my devices.
I mean it has been a steady decline but parent comment was suggesting that Firefox is probably near the floor of their market share.
Once people start hitting two 30s unskippable ads on every song they want to listen to on YT, they'll start searching on how to fix that. FF could capitalize on this trend.
Most of the users do not use ad-blocker and most of the users uses whatever browser come with their mobile device or Windows install.
I like it's disturbing monopoly, but it's rendering makes my life harder
It's just a repeat of the IE 6 debacle.
So you really can’t rely on usage figures that don’t represent the truth of your situation.
[1] https://github.com/mozilla/gecko-dev/blob/413b88689f3ca2a30b...
[2] https://blog.mozilla.org/en/products/firefox/firefox-now-ava...
https://www.npr.org/2023/09/12/1198558372/doj-google-monopol...
It doesn't particularly matter whether or not the figure is accurate in that context. Maybe that can be fixed easily by having Firefox contextually relax tracking a bit or by having the government change how they perform the tracking, but the status quo is not really sustainable. And that's really all the article is saying at the end of the day.
And they're involved with the Department of Education, although I couldn't find out exactly what they built.
They did help change over the old va.gov to the new va.gov (which was built as vets.gov), which imo has been a huge improvement.
(There are still many, many problems with the VA and its website. Just saying that 1. the new va.gov is a big improvement and 2. the USDS is far from being a single point of responsibility for it, or even _the_ major point of responsibility)
We also helped with design and infrastructure support for ssa.gov (launched earlier this year) with a contractor team to try to boil down 60,000 pages to ~30 pages that people tend to use.
// opinions of a former USDS, no longer with the team
Can you elaborate on what in particular on the VA site that causes serious harm to the people it's meant to serve? I'm happy to bring it to the team or if you don't feel comfortable with stating it here, please bring it up to the open source website for va.gov. https://github.com/department-of-veterans-affairs/vets-websi...
On top of that, said lack of knowledge is a stated goal of all privacy-focused browsers. GA-blindness is an implementation detail of these policies. Any method the government could use to accurately track that information is effectively a bug in need of fixing from the POV of the browser's developers.
The most practical answer is, as was posted by someone else here, the government spec'ing to a standard instead of a set of browsers, which it really should be doing in the first place. The mere fact that the current setup means that the government accidentally makes and/or breaks winners in that space is justification enough.
The most recent example I've run into is Snapchat's web client: It reject's Firefox purely by user agent string, but then works perfectly in Firefox if you just have your browser lie.
Speaking of Google, won't this interfere with their "look we're not a monopoly" payments to Mozilla Corp?
The government doesn't design roads to conform to the top brands of cars and trucks. It specs them to a standard and any manufacturer can have their product certified as compliant. This both protects the public and gives anyone an opportunity to provide products no matter how small their market share is. Doing it the other way around would be madness, and I don't see why the same principle shouldn't apply here.
This is exactly why sites should be tested for their conformance with the standard rather than with specific browsers. Testing against specific browsers just encourages browser-makers to continue to avoid fixing their shit.
When people complain that they can't submit their DMV forms (or whatever) and you say, "well we followed all the standards, go find another browser" and they say "which one" and you say "I don't know, we didn't test with any browsers, we just test against the standard" who do you think they'll blame?
Is it really a standard if the dominant vendor just ignores the standard and does what it wants because then it becomes the "actual standard" ?
As a (terrible) example, look at FIPS. The government has the power to mandate a standard that everyone needs to implement. If instead of "supporting specific browser vendors" they "support a specific standard" then all vendors have a target that works with an agreed upon common ground.
Plenty of standards are guidelines. The point is the website’s purpose trumps dogmatic adherence to a standard. If the site works against standards but not in the browser, it’s a failure.
Basically, no proprietary features whatsoever. No draft features. No optionally-supported standard features without a fallback that fully covers the same underlying use case.
This would be beneficial guidance for browser developers, but also for anyone developing government sites. Saying "whatever chrome is doing is our standard" is a cop out.
If you want test that you are adhering to a standard (if there is no testsuite available) you need to test against more than 2 independent implementations.
USDS serves basic pages and applets which work fine on Firefox. It is only a handful of very complex web apps like Photopea where the developer will say "run this on Chrome for best results".
They really should be hiring a pollster to ask people which browser they use. It might be a bit difficult for those who use the default, but it wouldn't be that difficult to ask a couple of followup questions (e.g. which device) to determine which default browser that is.
I think it's been the case for a good 10 years.
It works fine, of course
The browser support is currently listed at https://www.gov.uk/service-manual/technology/designing-for-d... . The mention of 2% is specific to IE11, so I guess this was special-cased at some point.
So, the default position of the government is, "If we can't surveil you, we can't help you?" (Or taken the other way, you want us to help you? Let us surveil you!) This seems to be how it works out in practice, just because of favorable economics in mass surveillance. Example: RFID and license plate readers for toll collection. Various registrations with government agencies are another example.
If Mozilla can't even play this card, then they should really just shut down.
Or, maybe, like Wikpedia, they should stop begging for more-more-more, and spend what they get wisely.
Not to mention, they could simply start bug bounties and/or crowdfunding for actual deliverables and/or services (ie. a security team).
And if all this fails, then it fails. Maybe we'll simply get a Firemium or Chromefox/fix whatever the name. A fork where adblock works.
It seems like a pretty bit conflict of interest when the #1 money source for Firefox comes from Firefox's only real competitor.
No browser deserves special treatment here. And this is as true for Firefox as it is for Lynx.
Naturally this enforced competition wasn't in Google's interests as its browser became dominant and it adopted the infamous Microsoft strategy to deal with the threat. Apparently we're fast approaching the extinguish phase.
The correct solution to this is for influential public bodies not to insist upon supporting any specific browser or browsers but instead to once again support open web standards and therefore free access to their information and services for all.
This is almost certainly in their own interests anyway. Google has a nasty habit of suddenly killing off its non-standardised extensions. Relying on functionality that other browsers don't necessarily support as well seems unwise.
How do you think WiFi devices work together? Is it because WiFi is a standard? Not really - it's because WiFi vendors all test their chips against other WiFi chips on the market.
Typically the cost of fixing the problem and going through the whole certification process again from the start is significant. There are some direct financial costs but mostly the damage is increased time to market. That's a great incentive for the maker to get their act together and comply with the standards like everyone else as quickly as possible. If you screw up too many times your product might be obsolete before you're ever allowed to sell it.
Not the kind of standards we are talking about.
Completely disagree. Privacy is a 4th ammendment right, so the government has a duty to support privacy first browsers. How am I "secure in my ... papers and effects" if I must use a privacy destroying browser to interact with the Government? If anything, chrome support is what should be questionable.
To say "we are going to support a browser with 2% market share because we like it more" would therefor be a really big deal. I think a far better avenue would be for the government to provide funding for privacy technologies directly, in an effort to increase their marketshare, and thereby making support of those technologies trivial to justify without any potential issues of bias.
The thing is, the government already does this. The majority of TOR's funding comes from the USG, for example. I'd suggest that maybe the government could fund Mozilla's non profit, to a degree.
This is all based on a premise that Mozilla is worthy of that funding. Is Mozilla really the privacy champion that it touts itself as? Would funding be contingent on anything else? If the government is so determined to prioritize privacy, why not Brave? Or some other entity? Or a new entity?
My understanding is that the consequence is denial of the right to privacy is limited to women while they are pregnant. Not a categorical denial of the right to privacy.
> The final decision was little changed from the leaked draft. Writing for the five-justice majority (with Chief Justice Roberts concurring only in the judgment), Justice Samuel Alito argued that the right to privacy is not specifically guaranteed anywhere in the Constitution. When unenumerated liberty rights exist — the right to raise your child as you see fit, for example — those rights must be “deeply rooted in the Nation’s history and tradition.” Reviewing the history of abortion restrictions in the early United States, Alito concluded that the right to abortion is not.
> The opinion ignited a firestorm of controversy. Predictably so: Dobbs is arguably the first case to formally rescind a fundamental constitutional right. The opinion also failed to explain how its logic would not also result in the overturning of Griswold’s right to contraception or a series of other cases that rely on the same logic as Roe. These include Lawrence v. Texas (2003), which invalidated laws criminalizing same-sex intimate sexual conduct, and Obergefell v. Hodges (2015), which recognized the right to marriage for same-sex couples.
Three is not a plethora.
Blink engine, Webkit engine, Gecko engine. Three.
That 2% kind be breached, but the data doesn't accurately represent usage if Firefix is blocking GA in any meaningful numbers.
Looking at browser usage data from GA when Firefox specifically blocks it quite often is useless.
Nepotism and bias aren't the alternative here. If you require that decisions are driven by data and you don't have access to accurate data, you should default to doing nothing. If anything, nepotism and bias sneak in when decisions are made despite the fact that no accurate data is avaliable.
https://en.wikipedia.org/wiki/Progressive_enhancement
Neglect would be a step up. It feels like they are actively trying to antagonize existing users.
This seems to be all that most software developers can do these days.
It would be best for the future of Firefox if they don't.
The decline has already been happening since around 2010 without any drastic ups or downs.
Might also be useful to have a plug-in to make a daily 'ping'/check-in from FFox to any govt sites used by their users. E.g., I use USPS and SBA/SBIR sites, but only occasionally or monthly, but if most FFox users who did so got logged more like daily instead of ~fortnightly or ~monthly, it'd improve the numbers. (Obviously, also must be done carefully so as to not get wholesale discounted).
The cascade effect of the US Govt abandoning support would be catastrophic, likely terminal, which would be bad for everyone.
That would be backwards
The main reason to use FF is the privacy protections
I find it very frustrating they do not get more recognition for the work they do on that front
GoAccess puts Firefox at 7.8% and Google Analytics at 3.3%.
GoAccess puts Chrome at 57% and Google Analytics at 73%.
For non-nerd populations, these numbers seem high.
There is an Android app that uses a webview so that even favours Chrome. Also GoAccess doesn't unfortunately filter all scrappers/bots and most of them declare themselves as Chrome.
A sizeable part of the traffic is (non-app) Android and I don't think Firefox is huge there so maybe on desktop Firefox market-share is actually not as bad as we think?
The default is Standard. It doesn’t block GA. The cynic in me suggests they decided making Firefox disappear altogether from popular stats by default would have harmed them more than not doing it harms their users, or that the backlash would be too great for their liking.
Sources like Google Analytics and Statcounter are still chronically undercounting minority browsers and platforms, which are much more likely to block these sorts of things, and Firefox and Linux will be particularly heavily hit, but I’m sure the difference it makes isn’t as large as I’d like it to be.
And how could Firefox possibly complete against default browsers? Is it even worth the investment?
It was so slow, it was unusable; even the first Android devices running on underpowered hardware were speed champions in comparison. Looking for an Whatsapp launcher was beyond the patience of even dedicated fans.
Sent from my Librem 5.
Safari is _really_ good and a very high bar to catchup to, even if you don't have to implement the rendering engine and Mozilla is not exactly known for their friendly and refined UIs. Vivaldi on iOS is much younger by comparison and looks a lot better than Firefox.
I disagree. For the purposes of this conversation, I feel like it's the only thing that matters. The web doesn't benefit at all from a WebKit-based browser by Mozilla capturing some of the iOS marketshare. Websites will still have to cater to WebKit. Not Gecko or something new
> Mozilla is not exactly known for their friendly and refined UIs
I actually strongly prefer the Firefox app's UI to safari
I believe it matters because it shows Mozilla's ability to market their product (Firefox). If they continuously fail to capture user base on any platform, then what powers Firefox is of little consequence.
As an experiment, I just installed Firefox on iOS just to see what's up and honestly 4 screens of things to confirm before I even get to the browsing part? As a tech person I understood each of them of course, but no sane person would put 4 screens in a row blocking users from using an app they normally already know how top use. So no, I don't believe Mozilla has the required UI/UX skills.
Apple sets the rules, gets special access (new releases, features, platform changes, countless other things), and relentlessly captures their users into the Apple ecosystem/moat. You seem to think swapping the rendering engine is a trivial task but you're asking them to practically create a new browser. And for all that effort, you're still competing with an opponent that's basically cheating. I'm not sure why Firefox/iOS even exists, frankly.
Ours:
Chrome 37.4% Firefox 24.7% Safari 21.1% Edge 7.5% Opera 2.6%
GA:
Chrome 39.3% Safari 31.5% Firefox 11.9% Edge 9.9% Samsung Internet 2.9%
For us, GA is undercounting FF by almost 13 percentage points, over 50%.
> this is Germany, generally far higher FF usage
But the interesting part is not how much FF has here, but how much GA undercounts it.
because google is using a near monopoly on analytics to bury a competitor in another segment
Truth of the situation is probably worse. We are losing users faster than anticipated.
The desktop is virtually dead for any "normal" user, and their Android or Apple tablet/phone don't prompt them with a choice (other vendor constraints notwithstanding). It's not remotely a fair fight. You are guaranteed to lose users for reasons totally outside your control.
Brave's BAT, while feeling kludgeful, is the only innovative idea in terms of funding sites nowadays.
Micropayments => dead Coil => dead (sorry, on a open stewardship) Flattr => unknown, guessing dead
So I want to block ads but I ain't depriving the websites of a way of earning money. If they want they can get my money -- but usually only that which was earned by wasting time to look at an ad.
Still, I disagree. Extensions can be bought and sold. It's difficult to track those things. I believe micropayments mechanisms should be integrated in the browser -- even if the provider can be changed.
https://stateof.mozilla.org/
https://news.ycombinator.com/item?id=38530382
https://www.ghacks.net/2023/12/05/mozilla-earned-close-to-60...
Firefox's market share has been on the decline since 2010.
https://gs.statcounter.com/browser-market-share#monthly-2009...
Genuine question. What is justifying Mozilla Corporation CEO Mitchell Baker's salary?
- 2022 - $6.9m/yr
- 2021 - $5.5m/yr
- 2020 - $2.6m/yr
- 2019 - $3.0m/yr
- 2018 - $2.4m/yr
- 2017 - $2.2m/yr
- 2016 - $1.0m/yr
- 2015 - $997k/yr
What a ridiculous question. Obvious the chief captain on the Titanic is not responsible for the Iceberg jumping at the boat.
Also important to label jokes.
in other words, for some people here it's not sarcasm.
Maybe if you'd referenced Chernobyl I would have picked it up sooner. Or THERAC, that's a classic.
Unfortunately, nowadays, unless you're among a group of people who already know your general opinions on things, it's nearly impossible to state an absurd position on some issue that a nontrivial number of people would actually, unironically, advocate for, until you get into the absolutely batshit stuff like "we should literally sacrifice poor people to the devil, then eat their flesh, to keep the rest of us from getting poor."
[0] https://en.wikipedia.org/wiki/Poe%27s_law
Salary has nothing to do with productivity at this level of an org.
That's nonsense. The difference at this level is you're not looking at personal productivity, you should be looking at a much broader interpretation. Except Mozilla doesn't. They've seen flailing commercial performance and have rewarded the CEO and laid off developers. It feels like madness because it is.
I love Firefox but Mozilla deserves to burn to the ground for this mismanagement.
That's one of the arguments made by CEOs who are trying to justify their insane salaries, yes. But it's very unpersuasive.
The question is how much you need to be to get a competent executive relative to the open market.
You can argue whether they’re getting what they’re paying for but this doesn’t seem to be out of line relative to the leaders of other, similarly sized organizations. Also a non profit has to have higher salaries as there’s not a lot of room to offload that to bonuses or equity.
No! The real question is what happens without an executive, but some cheaper leadership structure instead?
I mean, maybe a cheaper leadership structure (whatever it may be) would run the company into the ground, but, well, at least they would achieve the same outcome for cheaper.
What would Mitchell make as an SVP at a FAANG company? What could they make as a startup founder?
However in this case it doesn't actually seem to be paying off.
> Don't be snarky.
https://news.ycombinator.com/newsguidelines.html
I can imagine a similar analogy with M. Baker.
No, the CEO(and board) are completely responsible. That is the point of leadership, to move the boat before it hits the iceburg or at least have a way of dealing with it.
Firefox is buggy but heavily advertised(or astroturfed, I dont know) on social media. Everyone knows about firefox, we don't need the ad. We need firefox not to suck.
Not to pick on these two people, but it's interesting that they have senior directors for a conference and gift planning.
This branch of the company is often called "development," but R&D organizations sometimes need to come up with different names because that term gets overloaded.
[0] https://adnauseam.io/
Folks have raised concerns about Mozilla's funding from Google Search, but it's pretty clear from their past actions that they see supporting ad blocking as non-negotiable. Their diverging implementation of Manifest v3, while still incomplete (it's rapidly improving in 120, most of the remaining issues are related to Fenix support and Chrome parity), is thoughtfully designed to continue to provide familiar APIs for ad blocking.
The Mozilla board might be largely incompetent and/or corrupt, but they aren't actively trying to steal your data to profit from, and Firefox is still genuinely a less user-hostile product than Chrome.
As we are in the holidays and reflecting on things we are grateful for - Thank God for Linus!
Let Mozilla.org die.
Mozilla has proven to be really bad stewards, and as long as they exist nobody is going to pick up firefox. They've had many years to wake and up correct the course but choose not to, so it may be time to die. If Mozilla disappeared, a new organization could pick it up and run with it. If it weren't so overloaded in tech already, I might even call it "Phoenix" as it arose from the ashes of Firefox.
I have very few complaints about Firefox as software. I only wish more people would use it. (That includes you, dear reader!) It is actually great, and if you've ever complained about AMP, WEI or anything like that, using a non-Google derived browser is one of the few things you can actually do to reduce Google's power here.
Firefox are up against the power of OS defaults and dirty tricks in an age where most people don't really know what a web browser is. But if you have any awareness or concern about the health of the open web, you are absolutely educated enough to use Firefox. Of course there will be the odd minor workflow thing to get used to. But Firefox is great. All you really need is the motivation to choose something other than the default.
edit: username checks out.
If these numbers sound high ... $1M today was $500K in 1996.
https://www.levels.fyi/companies/amazon/salaries/software-en...
https://www.levels.fyi/companies/google/salaries/software-en...
https://www.levels.fyi/companies/apple/salaries/software-eng...
https://www.levels.fyi/companies/mozilla/salaries/software-e...
Looks arround the $170-200k level....
Yeah, at successful high performing trillion dolar tech companies like Nvidia or Apple, not broke*ss underperforming companies like Mozilla.
>6M for a CEO doesn't sound unreasonable.
It's unreasonable when you take into account Mozilla's lack of performance over the years. Where is their success, other than being kept on life support by being bankrolled by Google who's doing it solely to avoid anti-trust litigations over their monopoly on the browser market.
In a way, this is actually harming Firefox, knowing that they'll always be funded no matter how their product performs, just so that Alphabet has a legal David to their Goliath, gives them little incentive to try to be competitive.
Huh what? I use Firefox and I'm actually very happy with it.
I'm a happy user, I consider that a success in my book.
Or they do some batshit insane "polyfill" nonsense that turns the <button> into 56 layers of nested divs behind the hood.
HTML hasn't caught up either, there's no <toggle_switch> that invokes the native toggle switch that every OS already has, devs are forced to mimic the toggle with 85 layers of nested divs.
That's what what success means in this context: Something that makes that expense worthwhile.
If anything, the board should have gotten rid of her at this point and hired someone else, even if at this higher salary it would make more sense than sticking with someone who obviously hasn't been leading the company to growth or sustainability (since they are trending downards).
Be better
Nothing, of course. Absolutely nothing.
This question is why I don't expect Mozilla to last at its current course. I like their work, but the endless increases in CEO salary while their most important money maker is fledgling is not justifiable.
https://en.wikipedia.org/wiki/Mitchell_Baker#Negative_salary...
>>On the same period, Firefox marketshare was down 85%. When asked about her salary she stated "I learned that my pay was about an 80% discount to market. Meaning that competitive roles elsewhere were paying about 5 times as much. That's too big a discount to ask people and their families to commit to."
So I bet it's something like:
Baker: "If you don't pay me market rates for comparable work, I'll leave and go mess up a different organization."
Google: "No, wait, stop, we'll get you the money!"
Considering all the unforced errors on Mozilla's part, I'm only half joking there (i.e. that Google is influencing the decision, via their search placement deals, to keep Firefox bad).
Google says 'Don't spend your money on bug fixes and you can get 400M for default search, and you get your 3M bonus.'
Oops, we arent allowed to speculate on HN? I'm just jaded...
Unfortunately there will always be things to complain about and no system is perfect. But we have to make choices like this and these are the results. You cannot complain about Google's control/dominance over the web and refuse to turn away from their products to use reasonable alternatives (when they exist). Firefox is by no means a bad browser and it is easy to switch over. You can also still use firefox and complain about Baker's salary but is this really a killer issue?
I use Firefox on every device and I recommend others to do the same. That doesn't mean I agree with Mozilla, though, and their misplacement of funds make me worry about the future of Mozilla and Firefox as a browser. After firing the Rust team working on Servo, you'd expect austerity measures across the board, as Servo was clearly too expensive to continue investing in, yet Mozilla saw fit to continue rising Baker's wages, despite having just laid off 25% of its workforce.
I wonder about how much longer Mozilla will be able to exist. It's oriented around activism first, Firefox second, yet most of its income comes from its browser, and only because Google is scared of being branded a monopoly. If any other platform rises to popularity (and there are a few rising browser engines in the works, mostly as hobbies, but still) and Google switches to funding that project rather than Mozilla, I don't see how Firefox can survive.
Its decline is also visible in Mozilla's own data [1], 252M users in January 2019 down to 188M in November 2023.
MAU has remained at around 188M since October, I would like to believe this is because of MV3 and the YouTube drama, but that would be naive.
Going forward I think there should be a position on the foundation [2] and corporation board [3] held by a community representative. At least then the community would have some say in the direction Mozilla is taking.
[1]: https://data.firefox.com/dashboard/user-activity
[2]: https://wiki.mozilla.org/Board
[3]: https://www.mozilla.org/en-US/foundation/moco/
Mozilla is an open-source project. When an open-source project somehow loses its way, it's often forked by a new team of contributors who have a better idea. This happened several times: Open Office / Libre Office, MySQL / MariaDB, X86 / X11.org, hell, even GCC / egcs in the 1990s.
But this likely cannot happen to Mozilla, which is basically kept afloat by Google handing it some money for keeping it as a default search engine, about $400M a year currently [1]. There is little chance that an alternative "Better Mozilla" organization would collect as much, or at least half as much, to support a fork. It would e.g. take 33M users who agree to pay $5/mo for a Mozilla "support subscription" to collect $400M a year.
Maybe a web browser can be maintained for less than 400M, but likely not much less. The modern web is fiendishly complex, and you need both a desktop version (three platforms) and a mobile version.
[1]: https://www.pcmag.com/news/mozilla-signs-lucrative-3-year-go...
Perhaps ironically, this was also the genesis of Firefox
That's not entirely accurate (or at least, while accurate, is missing a lot of significant context) Mozilla was creating within Netscape, not in opposition to it, as a steward org for the open-sourcing of Navigator & Communicator. Even when Netscape was acquired by AOL, AOL continued to fund[0] Mozilla for years after the acquisition.
[0] https://web.archive.org/web/20050324025052/http://www.wired....
https://website-archive.mozilla.org/www.mozilla.org/firefox_...
Mozilla was created in 1998 to open-source Netscape Communicator suite. Mozilla released its own suite, also called "Mozilla" (e.g. "Mozilla 1.0" [0])
Independently of that effort, Dave Hyatt and Blake Ross made an experimenal, cut-down version of just the browser part of the suite, which they called "Phoenix", as in a Phoenix rising from the ashes. That's a fork. That's a fork by any metric.
They later rebranded Phoenix as Firefox, and eventually the Mozilla suite was abandoned. Mozilla changed tack in 2003 and switched to developing Firefox and Thunderbird as independent products [1]
[0] https://www-archive.mozilla.org/releases/mozilla1.0
[1] https://www-archive.mozilla.org/roadmap/roadmap-02-apr-2003
Maybe I'm reading this wrong, but when I do the math (33M x 5 x 12) I get $1.98B.
Maybe you meant $1/month?
The problem is that micropayments are not interesting for most news outlets: the friction of current solutions is high, the resulting revenue stream, unsteady. Monthly / yearly subscriptions bring a better revenue stream, and cost way less.
If micropayments were indeed zero-friction, and effectively zero-cost, maybe they'd be (reluctantly) integrated.
It makes sure that people who continue to use continue to pay. Upfront charges are often either too low with long term users free-riding or too high, in case the project is abandoned. Subscription makes it much more likely to price products correctly.
I could not disagree more. Subscriptions for software are a deeply unfair approach. Great for the companies, of course, but not for users.
A more fair approach is to charge for upgrades and support instead. At least that way, users only pay if/when they choose to obtain additional value.
If users want to stay on an old version, why shouldn't they be allowed to? Sure, there may be additional security considerations or missing functionality, but there's nothing wrong with a user making that choice.
It results in users having a broken experience or sites being very conservative in what features they use.
But the solution to this is to offer both forms, as several companies do.
Maybe we could go back to where people paid once and could pay separately for support?
This is a commitment to support the development, because the development should be oingoing. Not Netflix-style, but Patreon-style.
(Also see how JetBrains handles "subscriptions" to their closed-source software. Once you've paid, the version is forever yours. Updates are bought with some additional sums if desired.)
This simply does not exist for any software that is internet connected.
It's not feasible at all to call a browser "done" and leave it alone, so if you want one that's independent from adtech, a subscription is kind of your only option.
The EU does better than the US for consumer-related privacy issues. But I don't think the same can be said when the government wants to slap a label of "national security" onto something. That puts us into a whole different world of "anything goes".
If not this time then the next. Just the fact that the commission was allowed to propose such a blatant privacy invading law is enough for me to know that privacy is not a something that the EU is serious about.
Non-profit is better than gov but private is way worse than even gov.
But to think that the EU would be the guarantor of everyone's privacy on the web, is completely ridiculous.
Also your argument is not valid. When Google detects that you break their rules they ban your account. When the government has this kind power, then they have the power to do worse things to you, like imprisonment, fines, putting you on a blacklist and much more...
Those two things are not comparable.
Article 45 of eIDAS 2.0 will roll back web security by 12 years - https://news.ycombinator.com/item?id=38181114 - Nov 2023 (77 comments)
Joint statement of scientists and NGOs on the EU’s proposed eIDAS reform - https://news.ycombinator.com/item?id=38126997 - Nov 2023 (63 comments)
Last Chance to fix eIDAS: Secret EU law threatens Internet security - https://news.ycombinator.com/item?id=38109494 - Nov 2023 (299 comments)
EFF about EU: EIDAS 2.0 Sets a Dangerous Precedent for Web Security - https://news.ycombinator.com/item?id=33966364 - Dec 2022 (44 comments)
EU legislation eIDAS article 45.2 may force inclusion of insecure QWAC root CAs - https://news.ycombinator.com/item?id=32093891 - July 2022 (36 comments)
Mozilla and the EFF publish letter about the danger of Article 45.2 - https://news.ycombinator.com/item?id=30549119 - March 2022 (13 comments)
I doubt that. Mozilla wastes a ton, not only on CEO salaries but tangential projects and other dogoodery.
Mozilla is wildly profitable.
They made a profit of roughly 150 Million dollars last year.
They have 1.2 Billion dollars in assets.
They have increased revenue from non-search deals significantly (56M -> 75M, up one third).
Despite all the gnashing of teeth in this comment section about woke Mozilla, they spent only 5 Million on grants last year. The vast majority goes towards developing Firefox and building up assets.
I had always just taken the statements that she is absurdly overpaid at face value and never looked into this myself. But Baker has overseen the rise of revenue and net income from almost zero to current numbers. If that doesn't look like a successfully run NGO, what does?
Not a big fan of CEO compensation in general, but I feel the one-sided focus on market share, which I feel is somewhat out of Mozillas control (can't even compete on the dominant mobile computing platform, anti-competitive Google leveraging its search monopoloy and advertising Chrome extremely aggresively, etc... ), while ignoring the actual financial health of the organisation is really biased.
There are two parts to Mozilla: a for-profit company and a non-profit company. They are separate. You are reading the mission statement of mozilla.org, not mozilla.com. Mitchell Baker is the CEO of the for-profit company, not the non-profit.
Basically all revenue is made through the Mozilla Corporation.
If not, then the goal should be to build up assets and alternative revenue streams.
but in my opinion that isnt the reason google keeps firefox funded. i just think they do it for goodness sakes and not to cannibalize the only "competition". it really wasnt too long ago when it was chrome and firefox the two sleek awesome browsers saving the internet from nasty slow internet explorer.
It's pure fantasy to insist that the market share of Firefox is primarily driven by technical merit. Otherwise, you couldn't explain why Firefox is still at 20% in Germany, for example.
And I say this as someone who uses Firefox.
Firefox also has containers which (AFAIK) Chrome lacks. The UI for Profiles is probably worse, but Containers dramatically reduced the need for them for many (but by no means all) use cases.
It's definitely not the case that Firefox is behind here. I would say they are slightly ahead overall, but which of the Browsers is ahead depends on your specific use case.
It should be fairly obvious that this has nothing to do with the reason that Chrome has 10 times more users.
I've tried containers, maybe something got better, but I just simple, one window with everything in my work profile, another window, everything in personal, it's so easy to use in chrome. I can close the work window at the end of the day, and open it again the next morning, carry on
I'd love to feel optimistic about an increase in non-Google revenue, but 19M when the CEO alone is paying herself 7M of that alongside a 85M increase in expenses... it's still pretty hard to see it as a net positive here.
& of course the headline of this HN post is declining usage - that trumps profit either way imo
The same thing that is justifying obscene salaries in general. A circle of greed where obscenely paid people decide what obscenely paid people should be paid.
Offering a low-paying CEO role means you'll attract lower quality CEOs. The best CEOs have personal incentive to take the highest paying jobs. This element of competition does exist.
However, this ignores a few factors.
1. Mozilla don't seem to have a great CEO despite the pay.
2. Self-interest and CEO skills are not necessarily tightly coupled. They could be orthogonal. So a great CEO might be willing to take lower pay, especially a CEO that might be great for a company that is itself forgoing disgusting amounts of (ad) revenue in the interest of ethics.
3. (Not Mozilla specific but it's important to mention when this comes up) Decent regulations capping CEO pay would in fact remove this entire element of competition, freeing up companies from having to decide how much profit to sacrifice on the altar of business gods.
Maybe in the private sector.
> The best CEOs have personal incentive to take the highest paying jobs
It has to be said again: in the private sector.
Non-profit CEOs shouldn't expect to be compensated as well as their private sector counterparts. The feeling of doing good is part of the reward.
The relevant quote is "I learned that my pay was about an 80% discount to market. Meaning that competitive roles elsewhere were paying about 5 times as much. That's too big a discount to ask people and their families to commit to."
In other words, there's an assumption every corporation is required to have a CEO/Lawyer from the Technorati class who acts as a drain on the finances of the corporation, why should Mozilla be any different? Since the Mozilla Foundation is not a widely held corporation (and is a 501c3) there are only a few institutional directors ( from https://www.mozilla.org/en-US/about/leadership/#boards ): Baker (AOL), Chambers (McKinsey), Cooper (Walmart), Lakhani (MIT/Harvard), Lisbonne (Stanford GSB), Molotsi (Intuit) and Lund.
If you think Baker's pay should be cut, Lakhani is probably the person to talk to, he's chair of the compensation committee.
After watching VCs from the 70s to the current time (yes, I'm that old) I have a theory about tech startups. Their primary concern is to pump money from old school monied interests to old school monied interests' children. So if you have cash you want to give to your kids more or less tax free (or tax reduced), you send them to Stanford or MIT, then you arrange a meeting for them w/ your old school chum who's now a VC in San Jose or Palo Alto. You give the VC cash which is treated as an investment by the IRS, and then the VC gives the money to whatever bizarre tech startup is being run by their old school chum's kids. If you're lucky, you get a return on your investment and you pay whatever capital gains tax you need to pay (which is most often taxed at a rate considerably below that for earned income.) Your kids get a decent salary for a few years, and if they're lucky and smart, they git bought out by a big firm that makes them a VP or something. The VC should be lucky enough over time to make enough money on the 10% of deals that make it to acquisition to pay for the 90% that fail completely or get acquired on bad terms.
Mozilla always seemed to me to demonstrate this also works for non-profits.
Also... the story of "using money to transfer generational wealth in the upper class" is clearly not a universal. There are clearly startups that are innovative. They may be helmed by a handsome 20-something from Stanford, but that's just an historical accident. I am sure YOUR startup is in this category. But the "using VC investment as a money laundering scheme to evade generational tax" happens often enough my inner marxian shouts every time I drive down El Camino in Palo Alto.
And this part is purely opinion. I appreciate you probably have a different opinion and absolutely do not think less of you for having a unique perspective:
And besides, the goal of tech money is now just to keep the party going. The web is shit, intended to distribute content from major content producers or to be festooned with ads (twitch and youtube). iProducts are there to look sleek and provide just enough functionality to convince you to buy another iProduct. Though you're probably not in the target demographic anymore since China and India are at the beginning of the growth curve. Protocols and programs we used to use: SMTP/IMAP/eMail, (S)FTP/File Transfer, Veronica/Archie/WAIS/Search, etc. are pretty much dead or owned by Google, Microsoft or Yahoo's corpse.
I think the reason olds are nostalgic for Commo...
https://foundation.mozilla.org/en/what-we-fund/
Also, I don't think the US govt guidelines are going to have a dramatic worldwide impact on firefox numbers, the US is no longer the major online player it once was.
A few things that could go against this:
- If enough people use Firefox, no commercial business in their right mind will tell these people to "please leave, we don't serve your kind". Seems to be true for obscure versions of internet explorer still in use. Definitely true for Firefox for some time to come.
- Legislation might force the market to open up on mobile. Right now Apple is blocking the Chrome and Firefox rendering engines (well they allow similarly named shells around safari). And Google of course "owns" the search and browsing experience on Android by default and twists every OEM into signing a restrictive licensing deal. At least you can install firefox on Android. There are some signs this might start changing. A lot of outrage around privacy and ad blockers might speed this up.
- People can still vote with their feet. If you watch Youtube on a laptop and you don't have an effective ad blocker, Firefox is blocking them very nicely. I watch a lot of youtube and 100% ad free, just saying.
I don't believe Google will forever own the web. But, like Microsoft did, I believe they will cause us a lot of pain before they're through.
I am afraid to say in my world if Google degrades Firefox for YouTube most people I know will switch to Chrome
I have had success persuading people to switch to FF (I am one of those people) but a degraded YouTube- even the outright criminality that involves - would be a deal breaker
The ad blocking blocking will work the other way.....
They're not Spotify. They're not trying to growth hack. They don't need to look pretty and have fancy animations and match some designer's dream down to the pixel. They can add CSS etc. to make things a bit nicer, but government sites should work with as simple of a browser as possible.
Highly regulated critical infrastructure like banks should be required to do this too.
You're right of course.
It's not really a case of 'supporting' browsers, it's a case of testing their sites against other browsers in case developers have accidentally written some non-portable Chrome only code.
This was very much the case in the IE6 era. Developers wrote and tested their sites for and with IE6, and were then surprised they rendered (in)correctly on Firefox and looked wrong. At least these days there are shim libraries, rather than having to explicitly rely on things like the box-model hack.
But that's the point: rendering shouldn't really matter. For things that are important like government systems, we should treat web "apps" much like TeX encourages: you specify the semantics, and let the rendering engine do what it will. Don't try to precisely control it. You can and should assume that users can totally override rendering with a custom agent, that browsers will disagree on default rendering, and that they may ignore your CSS instructions.
Like if someone wants to use a browser that always renders h1, h2, p, etc. with specific fonts and colors, totally ignores any CSS, and adds buttons to each table column header to sort on that column, that should all just work. Or if you want to use a braille output or screen reader.
For important tools and information, not entertainment/shopping, functionality should trump all other concerns.
My bank and now my power company have issues where I need to use chromium to fill out a form, and I don't understand it. I know Firefox supports forms. For whatever reason, javascript is loading the thing and screwing up somehow. I don't see why js is even involved, but frankly it screams incompetence to me. The easiest thing in the world to build, and they've broken it trying to make it look nice.
I don't go to my power company website for fun. I'm there to pay a bill. I need a form with 5 inputs and a submit button, and that's it. The rest of the screen can be plain white for all I care. Literally something I could put together in 2 minutes when I was 11, and it does not work. Paper should not have a better UI than a website.
Incidentally, this is why I'm not too worried about AI. If companies wanted cheap/easy/reliable systems, that's been doable on the web the whole time. People can't resist making things difficult for themselves, and they'll pay very good money to do it.
If it's even possible for basic functionality to break in a way where you wouldn't obviously say the browser is broken, then you've built it wrong. That means you need to test that TLS/HTTP protocols are implemented correctly and that your documents conform to a schema.
Not in the real world. In the real world, you've delivered a site that doesn't work and contractually, you can be sued or not paid for not fulfilling your contract.
The government doesn't need to worry about market share. They can just dictate that this is what your browser needs to do to work with government systems. This is both more fair and easier for everyone; you don't have a moving target to aim for, and can just refer to the standard for what to do.
Governments exist to serve their citizens -- their users.
It's extremely user/citizen-hostile to say, "well our site works but no commercial browsers do, so I guess you can't register for a health plan this year over the web."
And I don't know about you, but I sure don't want the government building its own standards-based browser required for accessing government websites...
We could easily and reliably do forms on mainframes. This is not complicated. And de facto, every browser supports HTML 4 forms anyway, so that's a non-concern.
They already set standards for things like needing to support TLS 1.3 with specific cipher suites. There's no reason they can't say HTML 4 forms and links are required for browsers to work on their sites.
No -- I don't want the US government providing a reference implementation of web browsers.
No -- I don't want to log into a mainframe computer to fill out my taxes or sign up for Medicaid or a health plan.
The government should simply build services that work, in practical ways that are familiar and friendly to their citizens, according to the tools and habits their citizens are already accustomed to.
That means websites and apps for popular OS'es and browsers. It means phone numbers that work with existing telephones. It means offices in population centers.
Good governments come to where users/citizens already are. The shouldn't make users/citizens jump through hurdles to come to it, any more than necessary.
It's crazy to me that 10 years ago people were against the standard for government documents being essentially "whatever Microsoft office does", but in 2023, we've decided it makes sense for the standard for government web sites to be "whatever Chrome and Safari do".
And as I've pointed out, for historical reasons, we already have an adequate standard that the major browsers already support. So just target that standard. It happens that this is also the cheapest, simplest, most reliable way to do things anyway.
That's a position I just can't get behind. These are all just tools. The point isn't to follow some ideology, the point is to function.
And no, the government shouldn't formally "adopt" any specific W3C standard either, because standards evolve, and we don't want the government to get stuck in time. It should just write and maintain websites that work.
This isn't complicated. Businesses all seem to manage it just fine. The government doesn't need to do it any differently.
The "evolving" standards of browsers mostly add a bunch of useless toys that create security vulnerabilities. There's no reason for serious sites to target them. The old standards do everything you need to quickly and easily make a functional tool that will require no maintenance for years or decades, which is exactly what you want from tools.
The whole XHTML thing where allegedly it never caught on because people can't write valid markup has never made sense to me. They're able to get typescript to compile now, right? If a dev couldn't write react code that compiles, we would fire them, right?
We have tools to check that your document parses and conforms a schema. We've had them for 20 years. It's easy enough to have that be part of your CI pipeline. The tooling is 1000x simpler than modern frameworks, and the thing that was allegedly difficult was that if you enabled conformance mode (which was opt-in based on DTD and/or MIME type), you had to open and close your tags instead of just opening them. Surely any middle schooler understands when you open a parenthesis, you need to close it?
I worked on fibre channel networks at IBM. They were all about high touch customer service, and had great data gathering and would debug issues that ultimately were caused by some other vendor breaking the standard. After proving we were doing the right thing, our answer would always be to tell the customer to turn off the broken feature on their other vendor's device (other vendors would do things like inject fake ACKs for large transfers to reduce latency ("acceleration"), which is kind of a no-no in reliable networks. We lowered latency in a standard compliant way by using multiple concurrent exchanges that we put together at the application level).
We did test with some other vendors, but IIRC only at a fairly basic level, and didn't support any of their non-standard behavior. We just used them to validate our own compliance to standards.
If we try to stick to pure ideals without any consideration for reality, reality will ignore us and move on. Or, to borrow an example from another field: in infosec, the most secure computer is the one that's never turned on.
That's exactly what you need for "poorly funded" sites, and I don't see why a site that's meant to be functional needs a Hollywood budget.
First of all, that's just not going to happen for all sorts of practical reasons.
But secondly, you're totally ignoring UX and design. "Specifying semantics, and let the rendering engine do what it will" might work for developers who are used to interacting with API's. It will not work for regular users.
Regular users need to understand which button is the primary action. They need to understand which part of the content is the main body, versus a sidebar versus a header. They want columns that are correctly sized for their content. They don't want to have to scroll horizontally. They want responsive design that works on mobile too. They want something that looks trustworthy and familiar.
Websites are apps now. Asking to go back from presentation to semantics is like asking people to use the command line instead of GUI's. It's not going to happen, nor should it, because it's not user-friendly.
The only people it's friendly to are a niche set of developers with certain ideological beliefs that most web technologies shouldn't be used.
And government stuff should work differently from 99.9% of commercial websites. Again, the goal should be for it to work. The government does not need to do marketing and make you feel like they are trustworthy. If you want to interact with social security, you go to ssa.gov. If you want to interact with the IRS, you go to irs.gov. End of story. They don't need to act like commercial entities because they do not have to worry about market share. Their share is always 100%. They need to just make their stuff reliably work, easy to figure out, and should make it cheap and easy to build. Basic HTML with minimal optional styles checks all of those boxes.
If you view the computer as a tool instead of a toy, you see that you really just need most websites to be a more convenient version of paper forms. It doesn't need to look fancy. It needs some boxes to type information, it needs to always work, and ideally every form on every website would stick to the same 5 or so types of input (rendered consistently by your OS) with no surprises. Government sites should take the tool approach. Commercial sites can sell toys.
They do, though. People are able to figure out commercial websites orders of magnitude more easily than figuring out how to fill out their 1040.
> They need to just make their stuff reliably work
Which is what UX and design help with.
> Basic HTML with minimal optional styles checks all of those boxes.
It doesn't. Layout and design are tools that help with clarify and ease-of-use.
> you see that you really just need most websites to be a more convenient version of paper forms.
Nothing could be farther from the truth.
Do you similarly think that your iPhone or desktop interface would be improved if the UX was "a more convenient version of paper forms"?
Paper forms are an extremely limiting form of UX. Why would you ever want to throw out all of the progress we've made with usability?
Reliability is unrelated from UI, except insofar as simple UIs are easy to build, and therefore less likely to break. A paper form 1040 is perfectly reliable; it's not going to burst into flames when you're filling it out. As I said above, I couldn't even fill out my payment form on a modern site. It did not work at all. The form did not appear. That is not reliable. It also makes no sense if you know the page is ultimately using HTML, and that HTML has forms built directly in, and they always work fine.
And yeah, when I'm doing something like making a payment, setting up a transfer, doing my taxes, or even ordering a pizza, something like a slightly advanced paper form (e.g. with drop downs for options) would work great on my phone or desktop. Have a special request for your pizza that's not on the form? Put it in the free-form instructions box.
The "progress" we've made in the last few years is that I can't do bank transfers without switching browsers, which requires selecting a "to" account from a drop-down, a "from" account from a drop-down, and typing an amount. I don't see how something so basic can be so hard to do correctly. There's literally no need for any javascript at all. I don't see the usability gain from whatever they're doing.
Would an address lookup service be acceptable? One of those where you start typing your address into a box and it fills in all of the address fields based on which address you select.
If a new version of this is created, shouldn't it be tested on browsers? Which browsers should it be tested on?
Requires exactly zero lines of javascript, no third party api that may or may not work.
And no matter how "standardized" things get, there are always going to be implementation differences (whether due to mistakes or underspecified specs or partial implementation) and also just straight-up bugs between browsers.
Are people actually now using the older term, "shim," and not the newer "polyfill?" I was a grumpy old man when people started to tout the new terminology, when there were perfectly good terms already.
What parts of that are forcing you guys to be Chrome exclusive?
I can't say I have noticed much else, so I use chrome for gsuite and firefox for everything else ¯\_(ツ)_/¯
They work for me on Firefox 120 on Gnome 45.2.
A lot of the interesting people I follow are already using Gemini (though I remain unconvinced that that's a way forward).
1. Firefox blocks various analytics and tracking quite aggressively by default. Additionally, users of Firefox are, by and large, privacy minded and will have further mitigations. Any count of Firefox users is likely to be undercounting.
2. For the kind of basic web stuff(simple pages, forms etc) that USWDS supports it shouldn't matter greatly if Firefox is not supported. Theses standards are mature and Firefox supports them well, most thing should just work. Now, if websites go out of their way to block Firefox users that's a different problem.
[1]: https://radar.cloudflare.com/adoption-and-usage
---
But i doubt that will drive the numbers. On a side note, I think percentages will overstate firfox's decline. The number of devices with browsers per person will influence it heavily and that number is ever increasing.
I think the average person in my circle has more than 3 and many have more than 4 devices with they use to visit .gov sites (i.e. ipads, phones, laptops, but not including the fridge, car, tv, etc)
https://www.ghacks.net/2023/12/05/mozilla-earned-close-to-60...
Surely enough funding to keep going?
I understand things are bad, but this is a little too dramatic.