IMHO, the _moment_ we get rid of Firefox, the _moment_ we lost the free web. Building a web browser is just too damn hard, and never again would free software stand a chance. All will be Chrome-based, and Google will decide what "standards" to adhere to while it sits in a committee with itself.
That's what people said when I started to write an open-source DAW 22 years ago. "DAWs are just too damn hard, there'll never be an open source DAW".
Except that now there are several open source DAWs, and several proprietary ones, all created since that time.
I am very, very skeptical of claims like this. There is a reason why creating a new browser that lots of people will use is a challenge, but it's not because it's "too hard".
Browsers need to follow ever changing standards, do all that in a super performant way (remember the days people said they're leaving Firefox because Chrome "feels snappier"? Good luck beating that), keep it secure even though it's running remote code, and until they get it ALL 100% working, no one is really going to make it their daily driver. I already hear people saying that they're not using Firefox because some websites don't render well.
If it isn't "too hard", why do you think that over the last decade essentially no one managed to do it, while we do have several open source DAWs?
You don't have to beat Chrome at it's own game. I think the best course of action would be a drastic course change and building a browser that focuses heavily on the creation and publish of content, not just on the consumption. Focus on the Web as document storage instead of as App runtime. That's an area that is still in serious need of work and isn't really covered with Chrome. Also somebody really needs to reinvent bookmarks, they haven't fundamentally changed in 25 years and are in dire need of an upgrade.
Brave (IPFS and Crypto integration) and Project Gemini (focus on text content) are going a little into that direction, but there is still a lot more that could be done.
> Firefox because Chrome "feels snappier"?
It was less because "feels snappier" and more because "complete browser freezes when using multiple tabs". It has gotten better since then, but when Chrome started Firefox was in dire need of some rework.
In 1999, and maybe even 2011, a DAW that couldn't do elastic time was still considered to be a major player. In 2011, a DAW that couldn't do clip launching was still OK. In 2011, the idea of cross-routable modulation (like Bitwig now does) was a wild and crazy idea (mostly). In 2011, the idea of a modular environment within the DAW was floating around (Logic had done it for a while) but was hardly mainstream. These things are now either already or becoming more or less mandatory to be considered a major DAW.
Then there is the matter of control surfaces, which keep evolving. In 2011, the idea of a controller that was essentially a programmable grid of illuminated pads was mostly the domain of experimental performance (Monome). And every month or two, a new controller appears that claims to support Mackie Control Protocol, but has in fact bastardized it in some small but significant way. There's also the touch-based controllers, frequently using OSC, and their constantly changing suggestion of what should be possible.
And then there's plugin APIs, which also keep evolving, and we are under enormous expectation to ensure that every single one of many thousands of little code blobs written using one of a half-dozen plugin APIs and by developers with a range of experience that goes from nothing to world expert should all just work.
Over the years, we've also seen constant changes on Windows in terms of the OS-level audio APIs, each change bringing with it new possibilities and new problems. There's no POSIX for this. And, of course, a slow but steady evolution in audio interface hardware, which doesn't often impinge on the DAW itself, but sometimes does.
As for performant, browsers don't even have RT-style constraints, and there's plenty of observations about "snappiness" in this domain too. It's just a much smaller niche, and developer culture (as testified to by posts here on HN) is now very dominated by web-centric thinking and experience. As a result those sorts of things aren't really part of the culture in the way that "wow, Chrome is so fast" etc. has become. Look at the praise Reaper receives because of its (apparent) ability to handle more plugins with less CPU cycles.
As to why new browsers are rare ... I think it's because (1) browsers are not really fun at most levels, and (2) adoption is hard when there's a default on just about every platform. The fun part is important though. Many developers enjoy "messing around with audio" and it provides a kind of gratification that is rare (video stuff would be similar). It's not that cooking up a standards compliant and crazy fast and beautiful CSS implementation isn't without its joys, but there's so little point doing that as a standalone project. Contrast that with the steady drip, drip, drip of developers who want to try their hand at a synth, or an audio file editor, or FX processor and eventually think "oooh, how about a DAW". There's not really any evolutionary pathway for browser development: you're either writing a whole browser, or you're not. Audio gives you a way in, and then the sky's the limit.
The thing about Firefox is that it's an UNKNOWN evil. Mozilla always feel like it's on the cusp of bankruptcy and constantly searching for new dark patterns to sneak in. When Wikipedia needs money they beg for it, but don't purposely sabotage the user experience to get funding.
Mozilla does that with every new release. I always feel like they've added some shady new malware/adware with every new patch, and then use some stupid UI tweak to try to hide it. It's only a matter of time before they sneak Norton in there. I trust the Firefox team even less than Facebook at this point. Firefox just isn't trustworthy, whereas Chrome is a known compromise.
You trust the goons working for Facebook less than the goons working for Facebook? /s
It hit me really hard when during the whole FLoC controversy Mozilla published its own collaboration with Facebook on the future of browser based user tracking. No amount of technological hand waving could have fixed that first gigantic WTF and a description filled with privacy budgets, trusted third party servers, etc. didn't even have a snowballs chance in hell.
You provide valuable behavioural data to Google, which uses it to create very targeted demographics which are used for targeted advertising and analytics that are sold to advertisers.
Seen in this way, it’s quite darker than that, in my opinion.
I mean, our own government harvests even more data and does jack shit with it. At least Google provides a world-class office suite.
Was forced to used the Microsoft stack at a new job and it made me miss the Google ecosystem so much.
At the end of the day privacy isn't that valuable to people. Nobody cared about it in the 90s when the internet was developing, it was barely a blip in the 2000s, and somehow it exploded in the 2010s but plenty of people still use Facebook and TikTok and such. So?
Usability > privacy for most people, a lesson Firefox refuses to acknowledge, I guess.
The question for Firefox users is whether Firefox is on their side. If neither vendor is on your side, why not use Chrome? Has the UI on Chrome ever changed significantly?
> IMHO, the _moment_ we get rid of Firefox, the _moment_ we lost the free web.
I'd date this to the moment that the company that owns Chrome became the source of the vast majority of Firefox revenue, and probably all of its profits.
Mozilla are doing stupid things sometimes (and I've argued for that many times, in this thread, and in the Mozilla community), but they're just not even remotely as bad as Google. Firefox has containers, uBlock, tracking protection. It's literally the source for Tor Browser.
The question isn't a dichotomy of "who is on my side? none? so it doesn't matter". Firefox is still miles ahead than Chrome in privacy AND in keeping the web open. True, this doesn't make it perfect. But it sure does make it better, for all of us.
It's almost the same as old school Linux, where commercial software said "Hey I added this one click button for the main use case" and FOSS said "You don't need that, just have a bash one liner instead".
Chromium is openish. Other developers could fork it if they wanted to.
Firefox isn't doing anything about the fact that self hosting is way too much hassle for anyone but a few hobbyists. They're not really doing much in the IoT space.
They don't seem to be addressing the fact that the web is basically just Facebook and Youtube and Amazon in any way, except by adding ever-more tracking prevention tech that's not really relevant when all data goes through the same 5 sites anyway.
They actively get in the way of P2P tech by locking everything down so much it's impossible to implement a lot of things.
The lack of filesystem APIs just promotes even more vendor lockinful web services.
Mozzila does a lot of good things, but I'd rather they just switch to the Chromium engine, restore the removed features, and go back to what they were doing 5-10 years ago in the FlyWeb and WebThings era.
Every Firefox update on the other hand will always find one way or another to interrupt your flow at the worst possible option, whether it's with useless UI updates, post-update notifications about bullshit "features" such as Colorways or a VPN, etc. In contrast, Chrome's minimalistic UI has barely changed in its entire lifetime.
It's outdated and insecure, and I don't care. There simply isn't any other browser worth using for me.
(Though that may change now that there's a way to sacrifice all the new security features on current Firefox to run TMP again.)
