No it really wasn't. It took Firefox multiple years of catching up, releasing multiprocess architecture, 64-bit binaries (!), ... It took until Firefox 58 (2018) until they finally cought up. There was this huge period of nothingness around 2014 when they focussed on other weird stuff like FirefoxOS that everyone saw from miles away that it will flop.
Fun fact - FirefoxOS only flopped in Mozilla, it went on to be the insanely successful KaiOS based on the source code. KaiOS has over 100M active users.
This indicates there was actually a lot of technical merit in it and the problem was with the GTM and leadership.
No need to be revisionist. Chrome brought amazing work to the table. The multiprocess, sandboxed system was incredible - it's not to say that Chrome was the first (IE did it earlier) but it was certainly way ahead of Firefox for a long time. Chrome is the reason we have Seccomp V2 on Linux. Chrome made "software is always up to date" the standard. Before Chrome, Blackhole and PoisonIvy absolutely ruined people's computers - click to play Java, click to play and sandboxed Flash, etc, were massive improvements to every day user security, probably some of the biggest security improvements to computers in my lifetime.
Firefox took a long time to catch up and their CEO was utterly incompetent, which seriously harmed Mozilla.
I remember for a while that Firefox had a single process architecture for all tabs. This often frustrated me as one bad tab could just crash the whole browser while Chrome used separate processes for each tab, prompting me to switch to Chrome for a bit. Firefox caught up ages after chrome, and now I went back to them over the manifest v2 stuff.
Indeed. Around that era I had a fun little "crashmybrowser.com" toy site that had a few different JS tricks you could click that would absolutely wedge your browser (any browser, at the time). This had come after years of my being vocally annoyed that there weren't better guardrails around Javascript. Each of the functions was based on a real-world failure case.
Chrome was the first browser to be immune to all of those functions.
Mozilla really screwed the pooch not long after. Their biggest single misstep was forcing automatic updates in corporate networks. At the time, they still had pretty good adoption in the kinds of environments that had a couple of people somewhere deciding what everyone was allowed to run on the company computers. Chrome had already moved to forced updates, so these environments went to Firefox. When Firefox decided to follow Chrome, they no longer had that differentiation, and corporate IT had to choose between two browsers that both had automatic updates, but one of them had frequent memory and performance problems.
I've happily returned to Firefox a few years ago and don't have Chrome installed on any device I control.
Chrome's multiprocess sandboxing wasn't unambiguously good. It carried a steep cost in overhead.
Back when Chrome was new, you could run Firefox with a decent selection of add-ons to get security benefits of similar magnitude through different mechanisms. The NoScript extension was at the forefront, providing a lot of functionality way beyond just blocking JavaScript per domain. And Firefox with extensions always had better privacy controls.
I doubt there are many things in this universe that are unambiguously good, but Chrome's sandboxing is certainly as close as anything.
You can make your arguments about noscript if you'd like (I have a great respect for the project) but I think it was essentially irrelevant to user security at the time, real users were really harmed by malware that exploited Firefox, Java, and Flash, and Chrome killed every one of those attack paths in virtually no time at all.
Computers were far more dangerous before Chrome. You watch old TV shows and it's a joke that people would visit a site and get hacked - that's unrecognizable today, it simply doesn't happen. It used to, Chrome changed that.
> Chrome's multiprocess sandboxing wasn't unambiguously good. It carried a steep cost in overhead.
This is true, but this is why we create faster and faster PCs, so our software can do more. The cost was because you were getting new safety features. Want the app to be fast, able to show you lots of tabs with no delay? That takes RAM and CPU. The CPU and RAM are there to be used for features the user wants. It's actually 100% ok if a computer has to work really hard to run an app as long as that app is designed well, it means the user is making it do lots of useful work. That's what the computer is there for.
It is especially true for projects like Firefox which have access to massive funding since these attract the sort of people who consider those funds 'wasted' because they can be used to do so much for 'the common good'. Mitchell Baker - the utterly incompetent CEO - considered Firefox an afterthought because what the world needed was more NGO activism and what she needed was 400% more money for herself [1].
Wikipedia/Wikimedia is another example of a project with massive funding with similar problems even though the latter has a (not so) BDFL.
It was just less of everything than Chrome. First install experience for an average user was much better in terms of speed and snappiness. That was one of the keys to its success.
3. For a significant period of time (that continues to this day) websites were made using only Chrome as the target platform, turning Firefox into an eternal second fiddle that would occasionally break important/work websites.
No it really wasn't. It took Firefox multiple years of catching up, releasing multiprocess architecture, 64-bit binaries (!), ... It took until Firefox 58 (2018) until they finally cought up. There was this huge period of nothingness around 2014 when they focussed on other weird stuff like FirefoxOS that everyone saw from miles away that it will flop.
Fun fact - FirefoxOS only flopped in Mozilla, it went on to be the insanely successful KaiOS based on the source code. KaiOS has over 100M active users.
This indicates there was actually a lot of technical merit in it and the problem was with the GTM and leadership.
TBF KaiOS had a measure of success but it is now on life support.
The fact is Android could be scaled down way better than KaiOS could be scaled up.
(and you could just wait for the perf/$ to continue to decrease).
No need to be revisionist. Chrome brought amazing work to the table. The multiprocess, sandboxed system was incredible - it's not to say that Chrome was the first (IE did it earlier) but it was certainly way ahead of Firefox for a long time. Chrome is the reason we have Seccomp V2 on Linux. Chrome made "software is always up to date" the standard. Before Chrome, Blackhole and PoisonIvy absolutely ruined people's computers - click to play Java, click to play and sandboxed Flash, etc, were massive improvements to every day user security, probably some of the biggest security improvements to computers in my lifetime.
Firefox took a long time to catch up and their CEO was utterly incompetent, which seriously harmed Mozilla.
I remember for a while that Firefox had a single process architecture for all tabs. This often frustrated me as one bad tab could just crash the whole browser while Chrome used separate processes for each tab, prompting me to switch to Chrome for a bit. Firefox caught up ages after chrome, and now I went back to them over the manifest v2 stuff.
Indeed. Around that era I had a fun little "crashmybrowser.com" toy site that had a few different JS tricks you could click that would absolutely wedge your browser (any browser, at the time). This had come after years of my being vocally annoyed that there weren't better guardrails around Javascript. Each of the functions was based on a real-world failure case.
Chrome was the first browser to be immune to all of those functions.
Mozilla really screwed the pooch not long after. Their biggest single misstep was forcing automatic updates in corporate networks. At the time, they still had pretty good adoption in the kinds of environments that had a couple of people somewhere deciding what everyone was allowed to run on the company computers. Chrome had already moved to forced updates, so these environments went to Firefox. When Firefox decided to follow Chrome, they no longer had that differentiation, and corporate IT had to choose between two browsers that both had automatic updates, but one of them had frequent memory and performance problems.
I've happily returned to Firefox a few years ago and don't have Chrome installed on any device I control.
Chrome's multiprocess sandboxing wasn't unambiguously good. It carried a steep cost in overhead.
Back when Chrome was new, you could run Firefox with a decent selection of add-ons to get security benefits of similar magnitude through different mechanisms. The NoScript extension was at the forefront, providing a lot of functionality way beyond just blocking JavaScript per domain. And Firefox with extensions always had better privacy controls.
I doubt there are many things in this universe that are unambiguously good, but Chrome's sandboxing is certainly as close as anything.
You can make your arguments about noscript if you'd like (I have a great respect for the project) but I think it was essentially irrelevant to user security at the time, real users were really harmed by malware that exploited Firefox, Java, and Flash, and Chrome killed every one of those attack paths in virtually no time at all.
Computers were far more dangerous before Chrome. You watch old TV shows and it's a joke that people would visit a site and get hacked - that's unrecognizable today, it simply doesn't happen. It used to, Chrome changed that.
1 reply →
> Chrome's multiprocess sandboxing wasn't unambiguously good. It carried a steep cost in overhead.
This is true, but this is why we create faster and faster PCs, so our software can do more. The cost was because you were getting new safety features. Want the app to be fast, able to show you lots of tabs with no delay? That takes RAM and CPU. The CPU and RAM are there to be used for features the user wants. It's actually 100% ok if a computer has to work really hard to run an app as long as that app is designed well, it means the user is making it do lots of useful work. That's what the computer is there for.
1 reply →
NoScript and uMatrix were a great help - for very advanced users. But the typical user was left behind.
> Firefox took a long time to catch up and their CEO was utterly incompetent, which seriously harmed Mozilla.
This is basically whole history of Mozilla and to be honest most of open source projects that dont have BDFL type of leadership.
It is especially true for projects like Firefox which have access to massive funding since these attract the sort of people who consider those funds 'wasted' because they can be used to do so much for 'the common good'. Mitchell Baker - the utterly incompetent CEO - considered Firefox an afterthought because what the world needed was more NGO activism and what she needed was 400% more money for herself [1].
Wikipedia/Wikimedia is another example of a project with massive funding with similar problems even though the latter has a (not so) BDFL.
[1] https://calpaterson.com/mozilla.html
2 replies →
It was good, but slow by comparison at the time.
It was certainly better than IE but Chrome definitely surpassed Firefox and is still better except for blocking addons
It was just less of everything than Chrome. First install experience for an average user was much better in terms of speed and snappiness. That was one of the keys to its success.
> It was just less of everything than Chrome.
This is insane. As a power FF user, I don't think Chrome ever "got ahead". There were 2 reasons for its success (in order):
1. Made by a respected company that was killing everything in those days.
2. It was occasionally faster, and more stable.
Feature-wise - it was always worse.
3. For a significant period of time (that continues to this day) websites were made using only Chrome as the target platform, turning Firefox into an eternal second fiddle that would occasionally break important/work websites.
> 2. It was occasionally faster, and more stable.
That is ahead for the majority of people.