News for hackers. Stuff that matters.
Re:Mozilla’s Uncertain Future by causality0 on Saturday August 15, 2020 @03:38AM (#24166829)
Personally and strictly my own ignorant and informal opinion, Firefox and by extension Mozilla Corp. was doomed the moment it decided to compete with Chrome by being more like Chrome. Firefox built its userbase by being different than the dominant browser, then decided the only way to not die was to be exactly like the dominant browser except with less icky behind-the-scenes privacy behavior.

That was a fundamental mistake. The who's-got-the-biggest-version-number dick-measuring, the constant deprecation of power features and customizability, everything that was intended to beat Chrome in a contest Google couldn't lose is the reason Firefox can't hold onto a decent market share. The 25% of internet users who wanted what Firefox offered ten years ago still want the same thing now, but Firefox decided it was worth losing that 25% trying to chase the 75%, and they lost.

Re:Mozilla’s Uncertain Future by Brakenshire on Saturday August 15, 2020 @04:05AM (#24166971)
25% seems like much too high a number for the group you’re talking about. I’d be interested to see some data on level of technical engagement and knowledge, but in my experience a large percentage of users don’t even have a clear idea of what a browser is.

The reason Firefox has lost market share in my opinion is because:

i) Chrome is pushed by Google.com, which has a near monopoly on search

ii) Chrome was bundled and installed alongside other software

iii) Chrome is built into Android and Chromebook

iv) Chrome has a huge advertising budget

And all of these factors combine to make Chrome feel like the default portal to the web.

Also for a period of time Chrome was undeniably a better, more stable browser. It’s only relatively recently with Electrolysis and Firefox Quantum that Firefox has regained a technical parity or superiority. And those changes depended on specifying a proper UI and Extension API which is the reason why the browser is no longer so customisable.

But Firefox Quantum only exists because of Servo, and vital parts of Servo (parallel layout in particular) have not been integrated into Firefox. It’s bizarre to see Mozilla sabotaging its long term chance at technical leadership not only by scrapping Servo but firing the engineers who built it.

I had an untechnical family member say unprompted last week they want to move away from Chrome but couldn’t use Firefox Mobile because it’s too slow. At the same moment Mozilla leadership was sacking its staff working on parallelising the browser engine.

Re:Mozilla’s Uncertain Future by ksec on Saturday August 15, 2020 @07:53AM (#24168206)
>The reason Firefox has lost market share in my opinion is because:

My opinion is that none of those actually matters. The "one" single reason Chrome won market share was the same playbook how Google Search Engine Started.

Speed.

I watched hundreds of users, given the choice, or doing so themselves installing / using Chrome by their own selection. It was faster. The user experience was far better.

You could advertise the heck out of your product, but if it wasn't any good it wouldn't matter. For nearly 10 years Google Chrome was undoubtedly the fastest browser on the planet. It wasn't until Quantum landed on Firefox before you could at least have a few metric of performance wins going to Mozilla, and that is also partly because Chrome has slowed down a lot in recent years.

Re:Mozilla’s Uncertain Future by littlestymaar on Saturday August 15, 2020 @10:31AM (#24169132)
> I watched hundreds of users, given the choice, or doing so themselves installing / using Chrome by their own selection.

I don't know who you are, but having watched “hundreds of people” installing a web browser sounds a bit dubious…

Personally, I have discussed with a few dozens of websites users and most of them would answer the question “what web browser do you use” with “Google” no matter if they were using Chrome, Firefox, or IE (there are few Mac users in my country).

Firefox users had it installed on their computer by some computer-savy relatives, and most of Chrome users didn't know were it came from (most believing it was already there beforehands) which is a good marker of people getting it bundled with other pieces of software.

Re:Mozilla’s Uncertain Future by sdenton4 on Saturday August 15, 2020 @12:36PM (#24170151)
"having watched “hundreds of people” installing a web browser sounds a bit dubious…"

There's definitely jobs where this is possible... IT support at a medium sized company, various user research, etc.

Re:Mozilla’s Uncertain Future by baby on Saturday August 15, 2020 @01:35PM (#24170603)
I remember seeing non-technical people back in the days making the switch to chrome because it was faster indeed. Firefox had to do some catch up, and words of mouth didn't work in Firefox's best interest for quite some time.
Re:Mozilla’s Uncertain Future by jrnichols on Saturday August 15, 2020 @02:44PM (#24171205)
back in the early days I remember people switching over to it because it had a built-in Flash plugin. In more recent years, I've seen people installing it because they were sick of the pop-ups advertising it on Google sites, or they just assumed that it worked better with Google products because Google made it. Having learned that Google kind of made things that way, I'm not surprised.

Gmail was bait to lure millions into the Googleverse, where they usually don't leave.

Personally I'm kind of happy to see Microsoft Edge gaining some marketshare at Chrome's expense. (even if it's mostly just Chrome)

Re:Mozilla’s Uncertain Future by baby on Saturday August 15, 2020 @03:09PM (#24171400)
> because they were sick of the pop-ups advertising it on Google sites

for the longest time chrome advertising on google.com were actually malware : (

Re:Mozilla’s Uncertain Future by VRay on Saturday August 15, 2020 @01:37PM (#24170629)
This forum isn't some obscure backwater.. A large chunk of all the world's tech wizards congregate here during boring meetings, bathroom breaks, etc.

If someone claims to have done some work with tech, chances are they're telling the truth

Re:Mozilla’s Uncertain Future by craftinator on Saturday August 15, 2020 @03:56PM (#24171848)
This is a case of the problem of "most people are idiots in this realm". It pops up in many different domains.
Re:Mozilla’s Uncertain Future by otabdeveloper4 on Saturday August 15, 2020 @07:59AM (#24168246)
I actually bothered to load both side-by-side and check. Firefox loads pages faster.

Really the parent commenter is right: Chrome is dominant only because of its huge marketing budget.

P.S. Chrome is also buggy as hell and crashes pages all the time, which Firefox doesn't do.

Re:Mozilla’s Uncertain Future by jefftk on Saturday August 15, 2020 @08:27AM (#24168398)
> I actually bothered to load both side-by-side and check. Firefox loads pages faster

Are you comparing current Chrome to current Firefox? Relatively recently, compared to the overall trend we're seeing here, Firefox got much faster than it had been: https://blog.mozilla.org/blog/2017/11/14/introducing-firefox...

The discussion above, however, is about how Chrome came to grow so much while Firefox shrank so much, and for that the question is how did Firefox and Chrome compare historically. There was ~10y from Chrome's release until Quantum came out.

(Disclosure: I work for Google, speaking only for myself)

Re:Mozilla’s Uncertain Future by atesti on Saturday August 15, 2020 @12:50PM (#24170249)
Going fullscreen in youtube is always instant in Chrome. In Firefox however, it is very slow (like 5s) when you have 1000 tabs open.

Even opening a select box is slow, if you have several 1000 tabs.

Funny enough, opening a new window (and keeping all the other tabs open) makes it fast again, if you are in that window.

Seems like Firefox has some slow code paths, like notifying every tab about going fullscreen?

Re:Mozilla’s Uncertain Future by krzyk on Saturday August 15, 2020 @03:40PM (#24171685)
> Going fullscreen in youtube is always instant in Chrome. In Firefox however, it is very slow (like 5s) when you have 1000 tabs open.

Is it possible to have 1000 tabs open in Chrome? When I had like 50, it ate my whole 8GB last time I tried it.

In Firefox I frequently have 1000 tabs with no issues. (almost none, recently I noticed that there is some memory leak and the ram slowly disappears).

This is the reason why I went back to Firefox after using Chrome for like 2 weeks, it is great for 1-10 tabs.

Re:Mozilla’s Uncertain Future by atesti on Sunday August 16, 2020 @10:29AM (#24178104)
I don't know if anybody REALLY can have more than 1000 tabs open as in completely loaded into RAM. When my computer is slow I pray that I don't have any unsent edit windows or unfinished youtube/twitch videos and just kill all the render processes.

Chrome kills them regularly on it's own, which means they simply crash with out of memory.

For me, Chrome generally handles killed renderers better, e.g. it shows a popup about crashed extensions and just reloads them. Firefox requires me to quickly disable and enable adblock and I lose the build in screenshot extension permanently (except disabling and renabling it with about:config). But for chrome a renderer often just freezes and only a day later there is a popup about it which offers to kill it.

Firefox seems to handle the tabs better overall, but at some point session resume fails with javascript errors in the shell. Chrome seems to handle session restore a bit better.

Re:Mozilla’s Uncertain Future by mirthflat83 on Saturday August 15, 2020 @08:57AM (#24168529)
Yes. I remember when I first tried Chrome. It launched within 10 seconds while Firefox 3? 4?, my default browser back then, took almost half a minute to launch. It was fast.
Re:Mozilla’s Uncertain Future by rubber_duck on Saturday August 15, 2020 @09:42AM (#24168788)
That's relatively irrelevant - Chrome was much faster at the most important sites - which are coincidentally mostly google owned - but still faster - GMail, Youtube, Google itself felt faster on Chrome back then. Then there's the flash handling which was important back then.

Also FF was shitty at stability, it didn't have multi process architecture for the longest time and I've had a page crash my entire browser (especially in the flash days) regularly.

And then chrome started pushing excellent dev tools (even in FF nightly I get dev tools hanging on complex sites because of how slow they are)

Chrome was the better browser back then and it won the power users and developers, then it took over the casuals as it was advertised on google and it was recommended as the best by everyone - it took FF too long to catch up and now a lot of sites don't even test compatibility - I've been trying to switch back to FF before this fiasco for a month and it wasn't a smooth experience compatibility wise.

Re:Mozilla’s Uncertain Future by jefftk on Saturday August 15, 2020 @09:25AM (#24168685)
It sounds like you're describing how long it takes the browser to launch, when earlier you were describing how long it took to load pages? Browser launch time isn't nearly as important to most people as speed once running, because mostly you open the browser once, and then load many pages.
Re:Mozilla’s Uncertain Future by quicklime on Saturday August 15, 2020 @09:25AM (#24168687)
It's not just page load speed, although that is important. After the page load, some sites still feel slower (e.g. the new Facebook). It's also the speed of UI interactions, in particular detaching a tab is slower in Firefox than Chrome. All up, Chrome still feels faster to me.
Re:Mozilla’s Uncertain Future by ekianjo on Saturday August 15, 2020 @08:37AM (#24168444)
> I actually bothered to load both side-by-side and check. Firefox loads pages faster.

WHo cares? A Ferrari and a Lamborghini in 2020 provide about the same speed experience. What matters is that for the past 10 years Mozilla had the speed of an old Volvo versus the Ferrari that was Chrome/Chromium in comparison. The fact that Mozilla merely caught up in the end is rather a proof that they lost technical leadership a long time ago.

Re:Mozilla’s Uncertain Future by sanitycheck on Saturday August 15, 2020 @12:26PM (#24170059)
I used Firefox and Chrome simultaneously every day for many years on everything from a low-end laptop to pretty quick desktop. Firefox for personal stuff, Chrome for work.

Speed's always been similar for me, Firefox has generally been more reliable (partly due to being able to block so much crap, probably). Chrome used to break with alarming regularity and need a total reinstall. Sometimes there was a site which wasn't compatible with Firefox, and if I needed it I'd open it in a Chrome incognito window.

These days I've switched to Vivaldi for the work stuff (vertical tabs, "hibernate background tabs", tiling!), though I still debug JS in Chrome.

Re:Mozilla’s Uncertain Future by kwanbix on Saturday August 15, 2020 @09:17AM (#24168647)
Bs. The speed difference in real life was never that much.
Re:Mozilla’s Uncertain Future by mdoms on Saturday August 15, 2020 @04:06PM (#24171937)
I find Firefox much, much, much less reliable than chrome.
Re:Mozilla’s Uncertain Future by avasthe on Saturday August 15, 2020 @11:18AM (#24169464)
This.

To win over non tech people, there should be at least one "killer feature" out of the box.

In case of Google Chrome it was speed.

In case of Google search, it was quality of results.

In case of whatsapp, it was availability on all kinds of devices.

Etc..

Or enforced by organization etc.. that's different thing.

Re:Mozilla’s Uncertain Future by Certhas on Saturday August 15, 2020 @09:06AM (#24168571)
The managers at Google who authorized the huge as budgets clearly thought the ads did matter.
Re:Mozilla’s Uncertain Future by Voliokis on Saturday August 15, 2020 @08:03AM (#24168262)
> I watched hundreds of users, given the choice, or doing so themselves installing / using Chrome by their own selection. It was faster. The user experience was far better.

For the first time or because they were already familiar with it? Once you've established yourself as the "default", it can be ridiculously difficult to convince people to switch to something else. Google has executed this strategy perfectly and they know that there's nothing Mozilla can do or anybody else will do. And that despite the fact that Google clearly abused its dominant position in another industry to establish dominance in this field. I'm sick of Google abusing its position and I'm sick of people defending Google because it's a "free market". No, that's not how it works.

Re:Mozilla’s Uncertain Future by ekianjo on Saturday August 15, 2020 @08:34AM (#24168426)
> Once you've established yourself as the "default", it can be ridiculously difficult to convince people to switch to something else.

Not very believable as FF actually gained a much bigger market share than default IE over time.

Re:Mozilla’s Uncertain Future by irjustin on Saturday August 15, 2020 @09:10AM (#24168599)
The statement is believable to me once there's context added.

IE was a terrible browser. Everyone knew it and Firefox was better in every imaginable way especially for "web masters". The Firebug system was a godsend.

Firefox unseated IE because of how much better it was. Microsoft could not get its head straight in this particular case. Always a non-conforming, slow browser with far fewer features.

That's what it takes to unseat the default - you have to be multiples better before people take notice in serious ways.

And, Chrome did that beautifully by leaning into the one thing the masses cared about. Speed.

Those ads were so good - extremely viral. Did they show anything objective or real? Maybe... maybe not. It's what caught people's attention and then when they tested it themselves, they believed it.

Personally I tested it and it was, by a very noticeable amount - I was hooked. Took me a bit of time to get over the loss of Firebug, but mostly sentiment because Chrome's debugger was quite good.

If Firefox was the semi-truck, Chrome was the Ferrari. Both got me to A => B. With firefox I could carry anything, plugins, extensions, whatever I needed. But it was a lumbering giant. Chrome came with none of that at launch but it went fast - and people talked about it.

Those were the days.

Re:Mozilla’s Uncertain Future by Macha on Saturday August 15, 2020 @09:26AM (#24168695)
I'd also point out that tabs and adblock were compelling end user features to the extent that nothing any major browser has on its competitors today compare to. Sync is the closest to a compelling killer feature any browser has got to these days, and all browsers had it very quickly (except Safari, which doesn't have to care when you don't have a choice on iOS).

The fact that Firefox was faster than IE and any technical expert you asked for recommendation would prefer it due to better standards compliance/extensions/having the only devtools were really the icing on the cake.

Google also has the kind of trust amongst end users, especially non-technical end users, that Mozilla couldn't hope to have since Google has their hands in so many pies. And as a technical friend/family member asked to make a recommendation, if anything the incentive is to recommend Chrome to reduce tech support calls when HangoutMeetDuoChat/YouTube/Photos/their preferred google product is acting weird in Firefox again.

It's hard at this point to see what any browser could do to build that kind of end user feature lead again this far into the game.

Re:Mozilla’s Uncertain Future by treis on Saturday August 15, 2020 @03:45PM (#24171737)
>Firefox unseated IE because of how much better it was.

Nitpick, but Firefox never had the majority of the market or a bigger piece than IE. Firefox was on the way to reaching that but they peaked around 33% share before Chrome came along and ate everyone's lunch.

Re:Mozilla’s Uncertain Future by kwanbix on Saturday August 15, 2020 @09:27AM (#24168697)
Did you really measure the speed difference? I doubt it was that much. It was mostly about perception.
Re:Mozilla’s Uncertain Future by emteycz on Saturday August 15, 2020 @10:03AM (#24168925)
I really want to like and use Firefox, but the difference (on a top-end computer) is very noticeable and annoying. Perhaps Firefox should work on their perceived speed, if that's the difference.
Re:Mozilla’s Uncertain Future by Dahoon on Saturday August 15, 2020 @11:23AM (#24169504)
So you didn't measure it. Worthless opinions as to me on my gaming pc chrome is most definitely slower. Both are opinions and worthless without numbers.
Re:Mozilla’s Uncertain Future by stjohnswarts on Saturday August 15, 2020 @12:30PM (#24170096)
Real world benchmarks show they are neck and neck leap frogging each other all the time, so both of you are wrong; they're generally so close a human can't tell the difference, it's all biases these days unless someone shows you the numbers. Lots of people don't realize the extensions they add can also severely upset performance, but that's on the user. My 4 year old computer works just fine with both of them and 4 or 5 extensions.
Re:Mozilla’s Uncertain Future by seba_dos1 on Saturday August 15, 2020 @08:31PM (#24173711)
It also depends a lot on use cases and available resources. When on a single or just a few tabs, my perception usually favored Chrome, but in real usage I'm often keeping hundreds of tabs open and Firefox keeps being speedy enough most of the time while Chrome becomes unbearable very quickly.
Re:Mozilla’s Uncertain Future by Drdrdrq on Sunday August 16, 2020 @04:38AM (#24176232)
Agreed, with a caveat: on non-Google pages. Google is actively slowing down their pages on Firefox (or at least heavily optimizes them, but just on Chrome - which is the same).
Re:Mozilla’s Uncertain Future by ekianjo on Saturday August 15, 2020 @09:29AM (#24168709)
> The statement is believable to me once there's context added.

So, the statement does not mean anything anymore then. It should rather be: "it's difficult to unseat a technically superior product with an inferior one" which is patently obvious.

Re:Mozilla’s Uncertain Future by rndgermandude on Saturday August 15, 2020 @09:33AM (#24168730)
>It’s only relatively recently with Electrolysis and Firefox Quantum that Firefox has regained a technical parity or superiority. And those changes depended on specifying a proper UI and Extension API which is the reason why the browser is no longer so customisable.

No, they did not. Electrolysis was around before WebExtensions. Sure, Electrolysis wasn't backwards compatible and a lot of existing extensions had to rewrite part of their code to be compatible, and abandoned extensions were broken forever - or would have been once mozilla removed compat shims (unless somebody picked up the slack, which people quite often did). This was still a lot better than breaking every extension and forcing a new extremely restricted WebExtensions API that was a clone of the Chrome APIs but came with their own bugs and a lot of "TODO: implement actual API".

Quantum is just a PR term. The impact of Quantum-related changes to extensions was tiny if present at all (if the extension already survived Electrolysis).

The only reason that old non-webext extensions do not work anymore in Firefox at all is that they helpfully removed the actually code that would run the extension (but not really last I checked, it's still around to support mozilla-owned sideloaded/builtin extensions such as pocket).

comm-central (Thunderbird, Seamonkey) even implemented their own implementation of what was removed to get (restartless) old-style extensions working again, falsifying the claim that forcing a WebExtensions-only change was a requirement to get e10s/Quantum going.

Underneath it all, to this day most of Firefox is still javascript + XUL/HTML on the frontend with bridges (XPCOM, etc) to expose the C components.

PS: e10s shipped in v53, "old" extensions were only removed in Quantum, which was v57 (but not really removed, as I noted, just disabled for everybody except mozilla's own stuff).

I ran (and sometimes still run) a personal fork of 60esr (aka >57 ;) where I added back "old" extension support by git-reverting a few hundreds of lines of code that they removed.. That thing was Quantum too, all the Quantum perf/speed improvements were still present, and yet magically still supported all the old extensions I cared about.

Re:Mozilla’s Uncertain Future by stjohnswarts on Saturday August 15, 2020 @12:35PM (#24170145)
The quantum versions of firefox are a lot more stable than the previous generation. Probably because they cut down on how many things extensions could get their grimey little fingers into. Also getting rid of more XUL helped. The new firefox is scads better than the old one. Sure I miss some extensions but that just is what it is.
Re:Mozilla’s Uncertain Future by rndgermandude on Saturday August 15, 2020 @01:18PM (#24170462)
Why do people keep saying they got rid of XUL? It's just not true. It's still there to this very day. Just look at browser.xhtml (the main browser UI file); it's a mix of HTML and XUL and the body tag is particularly interesting.

    <html:body xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">
The first child element of that body is currently:

      <popupset id="mainPopupSet">
That's not HTML ;)

They are trying to replace XUL with HTML and made some progress towards that. For starters they removed most or all of XBL.

From the perspective of an add-on dev it wouldn't have made much of a difference, it used to be manipulating a XUL DOM, now would have been manipulating a mixed XUL/HTML DOM, in the future it would have been manipulating an HTML DOM, not much difference except for tag names and attributes names really, and the rest was js and css.

Re:Mozilla’s Uncertain Future by atesti on Saturday August 15, 2020 @12:54PM (#24170277)
I noticed the same thing when the certificate fisasco happend: There was this one special XPI file they pushed via Normandy and I installed it manually (it was posted in some discussion forms) to get my extensions running again without restarting Firefox.

If one unzips this tiny XPI, one finds javascript code which can directly install a certificate into the master store.

So there is indeed a very powerful extension system available, but only to Mozilla itself who can sign such extensions.

Probably all the old stuff can be brought back easily.

Please put your comment in a blog! Back then I searched for these topics and found nothing

Re:Mozilla’s Uncertain Future by rndgermandude on Saturday August 15, 2020 @01:24PM (#24170507)
>Probably all the old stuff can be brought back easily.

Not anymore. They removed/replaced a ton of stuff that only was used by extensions at that point. That might lower their maintenance burden, but for the most part it really was interfaces and code that hadn't been touched since the 1990, so it wasn't like it was a huge maintenance burden before.

That means it wouldn't be that easy to bring back the extension system where the old extensions would be able just run unmodified. But it would be easy enough to bring back newly created old-type extensions or modify existing old-style extensions to use whatever is present now instead of the old stuff that got removed.

But then again, old-style extensions had to check anyway if a new major release broke anything, and usually it did break some stuff for some extensions. It was the cost of doing business. Jetpack/WebExtensions could help with that; if you extension was simple enough to fit within their APIs.

In fx60 (esr) the removal of these "old" interfaces and other things hadn't progressed much yet, so I was able to just git-revert most of the removals that affected the extensions I care about and that was enough to run those extensions again without obvious bugs.

Re:Mozilla’s Uncertain Future by thro1 on Saturday August 15, 2020 @02:06PM (#24170896)
>I ran (and sometimes still run) a personal fork of 60esr (aka >57 ;) where I added back "old" extension support by git-reverting a few hundreds of lines of code that they removed..

Sir, I would really appreciate if you could share a patch for it.

Re:Mozilla’s Uncertain Future by rndgermandude on Saturday August 15, 2020 @02:09PM (#24170922)
Re:Mozilla’s Uncertain Future by causality0 on Saturday August 15, 2020 @12:22PM (#24170035)
but not really removed, as I noted, just disabled for everybody except mozilla's own stuff

That's fucking infuriating. You should write up a blog post about how easily you were able to turn them back on in Quantum.

Re:Mozilla’s Uncertain Future by rndgermandude on Saturday August 15, 2020 @02:00PM (#24170837)
Re:Mozilla’s Uncertain Future by gruez on Saturday August 15, 2020 @12:49PM (#24170239)
Can you share your patches? I'm still using 52esr in some very limited contexts and an upgrade would be great
Re:Mozilla’s Uncertain Future by rndgermandude on Saturday August 15, 2020 @01:58PM (#24170820)
I never updated them beyond 60esr and that thing is outdated and insecure as well. I don't really see a point in doing so now, other than to prove I did it.

But here is the important bit regardless: https://gist.github.com/formerextensiondev/50f3ebf563048e75f...

And even back then I was too lazy to actually properly "fix" it as you can see.

Re:Mozilla’s Uncertain Future by danieldk on Saturday August 15, 2020 @04:55AM (#24167229)
I think this hits the nail on its head, but I would add

v. Intentionally breaking other browsers subtly on Google properties.

i, ii, and v are directly from Microsoft’s 90ies/00s playbook and the regulators are sleeping.

Re:Mozilla’s Uncertain Future by m-p-3 on Saturday August 15, 2020 @07:29AM (#24168100)
It's disgusting that the search UI for Google in Chrome is different in Firefox. You can even see that it works fine if you switch Firefox user-agent to Chrome, so there's not even a compatibility reason behind it (and why should there be, we have web standards for a reason).
Re:Mozilla’s Uncertain Future by RonanTheGrey on Saturday August 15, 2020 @03:45PM (#24171742)
Google Calendar regularly breaks on Firefox. Switch to chrome? Nope not a bad deploy. Switch the user agent? Works fine.

Hard to say if incidents like that are intentional, passive aggressive, or accidental, but they happen pretty frequently.

Same with Youtube. Firebase console. GCP.

Re:Mozilla’s Uncertain Future by kinleyd on Saturday August 15, 2020 @04:53AM (#24167216)
<But Firefox Quantum only exists because of Servo>

Which is why, for the life of me, I just can't see the logic of firing the Servo team.

Re:Mozilla’s Uncertain Future by tarkin2 on Saturday August 15, 2020 @09:01AM (#24168545)
Hasn’t the quantum project been successful? It seemed like project accomplished to me. https://news.ycombinator.com/item?id=24164058

It’s not like they binned servo and decided not to use it improve ff. It did improve ff.

They seem to have decided that’s done and finished now. And there’s no longer any need to work on it - whether that’s a wise move or not is obviously up for debate.

Re:Mozilla’s Uncertain Future by kinleyd on Saturday August 15, 2020 @11:28AM (#24169551)
Quantum was just one of the milestones, albeit an important one. Servo continues to develop and pass on many more features to Firefox. Shutting it down is basically shutting the major pipeline of progress that has gotten so many of us excited over Mozilla in the past several years. The decision does not augur well for Firefox and Mozilla.
Re:Mozilla’s Uncertain Future by gruturo on Saturday August 15, 2020 @01:23PM (#24170495)
I concur, it’s quite insane. All their initiatives brought back tiny, tiny figures compared to the google search deal. And that deal is so profitable because Firefox still has a decent market share.

Torpedoing the technological future of their browser is bound to reduce that share, at which point Google will likely offer much less money.

They are basically shooting their one trick pony in a leg, deliberately. It’s.... not smart.

Re:Mozilla’s Uncertain Future by anonymousab on Saturday August 15, 2020 @01:54PM (#24170779)
It makes a ton of sense if you look at it from the perspective of what leadership has been seeing: All this effort on maintaining their own browser engine, met with continued decline and further irrelevancy. Despite best efforts, a likely trend towards disaster.

In the face of that, it would be reasonable to think that the cost is nowhere near worth the effort, compared to just adopting Chromium.

I think it'd be very easy for them to think that their goals for the modern web are not intrinsically tied to having their own, completely separate software.

Re:Mozilla’s Uncertain Future by stjohnswarts on Saturday August 15, 2020 @12:37PM (#24170162)
Because maybe innovation should continue? some of the teams I can see closing for financial reasons but the servo team? that's like slashing your own wrists to see what happens.
Re:Mozilla’s Uncertain Future by HugoDaniel on Saturday August 15, 2020 @05:54AM (#24167577)
Money and hierarchy
Re:Mozilla’s Uncertain Future by neverminder on Saturday August 15, 2020 @08:41AM (#24168465)
> I had an untechnical family member say unprompted last week they want to move away from Chrome but couldn’t use Firefox Mobile because it’s too slow. At the same moment Mozilla leadership was sacking its staff working on parallelising the browser engine.

That's because Firefox is slow. I'm saying this as someone who's been using it as the main browser for at least a decade.

My latest personal anecdote. Firefox trackpad scrolling is lagging on my brand new Precision 7750 with vanilla Ubuntu 20.04 installed. Chrome doesn't have the same issue, especially considering Google's unfriendliness towards Linux.

Re:Mozilla’s Uncertain Future by alcoholic_byte on Saturday August 15, 2020 @10:31AM (#24169134)
Cannot verify and I am on Linux for a couple of years and on different hardware during those years. Arch-distribution, so maybe the defaults are what is different here?? Browsing, scrolling(with trackpad and without) startup time, etc. all fine. One thing that I find interesting to always ask: Performance under what circumstances? There are users who have literally 200 tabs+ open and then they complain that everything is slow.
Re:Mozilla’s Uncertain Future by gregors on Saturday August 15, 2020 @11:06AM (#24169380)
If users have 200+ tabs open and are experiencing slowness, I'd suggest that altering the users behavior isn't a fix. To me that's pure failure from Product designers to realize that "they shouldn't do that" doesn't cut it. Fix it.

Spending time and money on solving these issues isn't going to generate new revenue. I find it hard to believe engineers wouldn't want to try fix performance issues. I find it easy to believe leadership at Mozilla would find it unimportant.

edit: clarification

Re:Mozilla’s Uncertain Future by alcoholic_byte on Saturday August 15, 2020 @11:25AM (#24169523)
I think you are wrong there. As a product designer one never caters to edge-cases. Besides having 200+ tabs open is very impractical, the way Chrome minifies all the tabs instead of making them slidable is just one prime example where the designers chose not to cater to the extreme. Even with a tab-behaviour like Firefox's it is a very unmanageable situation. Also note that one might encounter a tradeoff in system-design where you could choose a very memory/resource-efficient design over a very performant one. You cannot always get both.

Unfortunately, because Google is "In" just because it delivers mind-numbing ease via Youtube etc., this very vocal minority, claiming technical expertise scew impressions for the general population.

Similar to absolute views like :They do not care... I think they care, not about the particular problem, but the product and how it meets the requirements of a general audience swiftly and reliable. So the problem crossed their desk, they triaged it and closed it because it is an extreme use case which will not meet general requirements.

The same goes for all the multitudinous problems in that area.

Re:Mozilla’s Uncertain Future by gregors on Saturday August 15, 2020 @11:46AM (#24169690)
I wasn't necessarily meaning the visual experience of having tab inception open, more along the lines of people feel that FF is slow. The 200+ comment was based around that there were quantifiers - it's the users fault for having slow software. "You're just doing it wrong".

From a Product perspective Chrome is the better product. I want to believe that Mozilla is capable of making FF the better product. Maybe it all boils down to Youtube and Facebook and in actuality it's impossible and they can't actually have a better browser. I don't really believe that. I do believe that Mozilla isn't on a trajectory to make that happen.

Re:Mozilla’s Uncertain Future by alcoholic_byte on Saturday August 15, 2020 @12:28PM (#24170078)
Luckily what you and I believe is irrelevant, unless we try to convince the masses by screaming at them long enough.

I wasn't referring to the tabs either, just as an example of people doing it wrong. No one stops them, but in the old days natural selection took care of it. These days people think, because they have a misconception, they have a right to an opinion which a misconception is not. This is known as "The terror of the masses". Desinformation and Fanboydoom(we against them) is based on that.

Yes FF was slow some 5/7 years ago, but speed up quite a lot. See here https://arewefastyet.com/win10/overview?numDays=60 . You can, of course, choose the Benchmark proving your point, or look at the bigger, quite different, picture. And just because 200+ people write the same comment in spirit does not make it true (see benchmark-site) . Also, as I have pointed out elsewhere in this thread, it is not just about speed. I agree that a site should not be agonizingly slow to work with, but that is not the case with FF (see benchmark). As far as the reference to the trajectory is concerned, it is not s.th. that securely predicts outcome. You never know what the future holds. Just think of the situation of MS or Amazone some 10-15 years ago. Besides Youtube and Facebook have nothing to do with the browser; also note that Alphabet purposefully sabotaged their own website so that it performed bad or even breaks on a non-Chrome browser. https://www.zdnet.com/article/former-mozilla-exec-google-has...

I would also like to remind the reader and you that I never said that the fault is with the user, I merely stated that you cannot demand a product owner, ANY product owner, to cater to ALL and EVERY extreme edge-case.

But since this debate of ours, I fear so, because you tried to warp above said statement of mine, is in danger of devolving into a fan-boy flame thread, let me close this with a quote I read in a facility of a philosphical faculty, in hopes that it gets people thinking before they regurgitate other people's/trolls/campainers opinion/misconception unreflected: "People, eat feces, for a 1000 flies cannot lie."

Re:Mozilla’s Uncertain Future by anonymousab on Saturday August 15, 2020 @01:59PM (#24170827)
>As a product designer one never caters to edge-cases.

The edges are where some of the most faithful users live. But you're right, it's becoming more and more clear, over various updates and certainly with the recent news, that Mozilla thinks they could do without the trouble and their PMs act accordingly.

Whether it's an issue that only one in a hundred users has to deal with, or an issue that every user has to deal with once in hundred of their actions in a browser session, an edge case is just an edge case.

Re:Mozilla’s Uncertain Future by neverminder on Saturday August 15, 2020 @02:55PM (#24171292)
I've been using Linux for a lot longer and on variety of hardware. I don't have this problem on my desktop, but the laptop and the trackpad are rather fresh, so maybe somewhere there's a bug or something. For some reason whenever there's a problem it's always Firefox, and rarely if ever Chrome. Example of another problem I had recently - websites like whathifi, tomsguide and a bunch of others were using 100% of one CPU core on Firefox, no problem on Chrome.
Re:Mozilla’s Uncertain Future by KingOfCoders on Saturday August 15, 2020 @04:35AM (#24167125)
I left FF several times for being slow, being a memory hog, dropping extensions, not adding power features (vertical tree tabs) and come back from Chrome for ideological reasons. I might not be the core audience or user group, but I have not left because of i.) - iv.).
Re:Mozilla’s Uncertain Future by Lammy on Saturday August 15, 2020 @06:56AM (#24167951)
> not adding power features (vertical tree tabs)

They made a pretty huge deal about the Tab Groups (aka Panorama) feature of Firefox 4 in 2010; designed by Aza Raskin! https://web.archive.org/web/20101105212333/http://www.azaras...

But then it was removed in 2016 because few people really used it (or few people who had telemetry enabled, at least): https://support.mozilla.org/en-US/kb/tab-groups-removal

Re:Mozilla’s Uncertain Future by badsectoracula on Saturday August 15, 2020 @09:16AM (#24168637)
Relying on telemetry has been the biggest mistake developers decided to do in recent years. In the vast majority, only the most technically illiterate will keep telemetry enabled. For anyone with enough knowledge and two braincells to rub together, telemetry is an euphemism for spyware, so of course they'll do everything they can to disable it (also see all the Windows 10 "shut up" scripts, etc - people would rather run random scripts from the net than allow telemetry, even if doing the former isn't exactly that smart to begin with).

Relying on telemetry is heavily biased towards people who do not know what telemetry is.

Re:Mozilla’s Uncertain Future by fartcannon on Saturday August 15, 2020 @08:59AM (#24168536)
Oh jees, is that what's happening? If they're only building for telemetry data, theyre screwed. Gonna end up with a browser for people who think the internet is a series of tubes.
Re:Mozilla’s Uncertain Future by chowells on Saturday August 15, 2020 @11:24AM (#24169515)
You believe developers don't understand telemetry and leave it enabled because it helps development of the tools they use?

This whole anti-telemetry outrage is so manufactured and boring.

Re:Mozilla’s Uncertain Future by csande17 on Saturday August 15, 2020 @01:04PM (#24170362)
I'm a developer, and I disable telemetry whenever possible, including in Firefox. I do this because I value my privacy (the same reason I use Firefox), and I don't want my system to make network requests unnecessarily. The way I see it, there are two possibilities:

(1) A significant portion of Firefox users think like me. In this case, Mozilla should not rely on telemetry because it excludes a sizeable portion of their userbase, and one that likely correlates with things like "believes in Mozilla's stated core philosophy" and "is passionate enough about browsers to recommend them to people".

(2) Not many Firefox users think like me. In this case, it's pointless for me to enable telemetry because they'll just ignore my needs anyway. "It is not worth supporting this feature, the data shows that 99% of people do not use it!" won't change if the number is actually 98.99%.

Re:Mozilla’s Uncertain Future by pikelet on Saturday August 15, 2020 @02:39PM (#24171174)
That's like saying your vote doesn't matter so there's no point in voting.
Re:Mozilla’s Uncertain Future by csande17 on Saturday August 15, 2020 @02:57PM (#24171316)
It would be like saying that, if voting involved putting a machine in my house to report information about my daily activities to the government, and they used that data to attempt to determine which candidates and policies I would prefer without actually consulting me.
Re:Mozilla’s Uncertain Future by hvis on Saturday August 15, 2020 @08:05PM (#24173563)
Re:Mozilla’s Uncertain Future by Lammy on Saturday August 15, 2020 @09:41PM (#24174107)
I was already a full-time Tree Style Tab user by the time FF4 Beta came around in 2010 so I'm probably part of the reason Panorama wasn't popular enough :p
Re:Mozilla’s Uncertain Future by hvis on Sunday August 16, 2020 @06:44AM (#24176745)
There's enough space for both UIs. ;-)

More importantly, it seems both of them have survived the move to Quantum. It was really hard for me to imagine going without Panorama.

Re:Mozilla’s Uncertain Future by forgotpwd16 on Saturday August 15, 2020 @05:35AM (#24167474)
One of the reasons I'm still on Fox is tree-style tabs (with "Tree Style Tab" extension) and being able to hide top tabs (using userChrome.css).
Re:Mozilla’s Uncertain Future by bishalb on Saturday August 15, 2020 @06:25AM (#24167756)
The best things about tabs in Firefoxia the scrollable tab bar. I am not sure why chrome doesn't add this.
Re:Mozilla’s Uncertain Future by emteycz on Saturday August 15, 2020 @10:09AM (#24168962)
Can you imagine having to respond to all these "chrome ate my tabs" tickets?
Re:Mozilla’s Uncertain Future by majewsky on Saturday August 15, 2020 @12:18PM (#24169976)
As if Google ever replies to tickets.
Re:Mozilla’s Uncertain Future by aldanor on Saturday August 15, 2020 @08:30AM (#24168408)
Same here. If TreeStyleTab existed on Chrome (or, hell, even in Safari), I wouldn't care that much which browser to use.
Re:Mozilla’s Uncertain Future by KingOfCoders on Saturday August 15, 2020 @09:54AM (#24168858)
I recently switched to "Simple Tab Groups" after years with "Tree Style Tab" and I do prefer it.
Re:Mozilla’s Uncertain Future by Brakenshire on Saturday August 15, 2020 @04:58AM (#24167237)
I just don’t think there are enough users who care about deep customisation through extensions compared to those who care about speed and stability, and Firefox traded one for the other in adopting a standardised Extensions API, and the changes that allowed in the browser architecture.
Re:Mozilla’s Uncertain Future by ohgodplsno on Saturday August 15, 2020 @04:50AM (#24167204)
> not adding power features (vertical tree tabs)

https://addons.mozilla.org/fr/firefox/addon/tree-style-tab/

?

Re:Mozilla’s Uncertain Future by stekern on Saturday August 15, 2020 @05:30AM (#24167438)
I assume the parent means native support for vertical tabs in the browser as opposed to through a third party extension.
Re:Mozilla’s Uncertain Future by KingOfCoders on Saturday August 15, 2020 @09:54AM (#24168865)
a.) Yes

b.) With changing their extension API several times it was not clear the plugin would make it.

Re:Mozilla’s Uncertain Future by stjohnswarts on Saturday August 15, 2020 @12:28PM (#24170077)
the current mobile firefox browser works great and it's not "too slow". They just simply didn't like their experience and told you it was "too slow" because they're biased again new things. Benchmarks (real ones on real web pages prove it) I agree with you though that Chrome engines are just everywhere and it's going to take some big sea change for that to not be the case.
Re:Mozilla’s Uncertain Future by robertlagrant on Tuesday August 18, 2020 @10:54AM (#24199353)
It is a bit slow. It loads some stuff it thinks I want to see before letting me type into the one input box, which isn't even focused, so I have to tap in it to summon the keyboard), and only then can I type something.
Re:Mozilla’s Uncertain Future by anonymousab on Saturday August 15, 2020 @01:49PM (#24170730)
>which is the reason why the browser is no longer so customisable.

That was the big one that cost a lot of users, but it was a jusitifiable big leap for them to take.

But they have also been suffering papercut after papercut power user losses with various regressions and removal of functionality since then.

The actual users lost are minimal, but I suspect the overall perception of Mozilla's priorities, among those kinds of users, has suffered much more.

Re:Mozilla’s Uncertain Future by outadoc on Saturday August 15, 2020 @04:14AM (#24167017)
> the constant deprecation of power features and customizability

They made ONE switch to a superior and standard extension model, and HN loses its minds. Do you really think you're in the majority here? Making it a more secure, faster and just better browser is just the only way forward. Without that Firefox would just be slow as hell, wouldn't play YouTube or Netflix videos, and not have any extensions left because no one wants to create an extension from scratch just for Firefox.

They tried their best and I hope it's been enough, even though the future looks bleak.

Re:Mozilla’s Uncertain Future by forgotpwd16 on Saturday August 15, 2020 @05:23AM (#24167387)
The WebExtension API even years later is afaik still less capable than XUL. They also deprecated plugins (NPAPI), a recent version has disabled userChrome.css and userContent.css by default and the pref is noted as legacy and the same is now considered for user.js if not removed. Also you cannot set a locally-hosted newtab page any longer.
Re:Mozilla’s Uncertain Future by marcinzm on Saturday August 15, 2020 @10:24AM (#24169074)
>The WebExtension API even years later is afaik still less capable than XUL.

XUL extensions were an ungodly mess and arguably hurt Firefox more than they helped. Stability, performance, etc. issues were common to be caused by them. Which when everything is in a single execution context is not fun. Most of the popular extensions simply hijacked random internal Firefox functions which is why they couldn't just be installed together.

edit: I wrote the first Tag Groups extension back in the XUL days so I contributed to the mess.

Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @12:16PM (#24169963)
I also wrote extensions and I did not find them to be an "ungodly mess". XUL was rather pleasant to work with compared to some of the other technologies I was programming with at the time
Re:Mozilla’s Uncertain Future by marcinzm on Saturday August 15, 2020 @02:54PM (#24171285)
They were an ungodly mess, in my view, compared to modern approaches which is what matters in the context of this discussion. The issue also wasn't XUL but everything else related to how extensions functioned (same JS context as literally everything else, no processes, internal FF methods were being patched by extensions, etc.). Their power came at a great cost and their approach is inherently infeasible in today's security conscious world (even if you ignore the stability and performance issues).
Re:Mozilla’s Uncertain Future by Multicomp on Saturday August 15, 2020 @07:34AM (#24168118)
They also killed off Live Bookmarks. I used that for years in FF and then later Waterfox until the PrivacyOne buyout, now I have to open a separate program to read my rss (rssowlnix)
Re:Mozilla’s Uncertain Future by athms on Sunday August 16, 2020 @10:06PM (#24183174)
Live Bookmarks died because it was ancient code that needed to be rewritten, but most people didn't use the feature. Mozilla added telemetry to analyze feed usage and the results came back with less than 1%. It was about resource allocation for development and no volunteers came forward.
Re:Mozilla’s Uncertain Future by ihuman on Saturday August 15, 2020 @02:14PM (#24170966)
> you cannot set a locally-hosted newtab page any longer

You can still set it with firefox.cfg, it's not not documented anywhere, and will break sometime in the future

  var {classes:Cc,interfaces:Ci,utils:Cu} = Components;
  var customNewTabURL = "file:///C:/File/Path/Here.html";
  Cu.import('resource:///modules/AboutNewTab.jsm');
  AboutNewTab.newTabURL = customNewTabURL;
Re:Mozilla’s Uncertain Future by boring_twenties on Saturday August 15, 2020 @02:34PM (#24171151)
> will break sometime in the future

To be fair, with Mozilla, it would break sometime in the future even if it was documented.

Re:Mozilla’s Uncertain Future by badsectoracula on Saturday August 15, 2020 @09:21AM (#24168662)
> switch to a superior

It is so superior that to this day, Downthemall - an extension which is literally all about downloading - cannot even let you choose an arbitrary directory to put the files you downloaded.

> and standard

That was Google's "standard" that Firefox decided to adopt and even if Firefox decided to implement it, there was no reason to not also keep its own extension system - this way it would be able to have both its own advanced extensions and Google's functionally inferior extensions, essentially making it the most extensible and customizable browser by far.

Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @12:19PM (#24169998)
> > switch to a superior

> It is so superior that to this day, Downthemall - an extension which is literally all about downloading - cannot even let you choose an arbitrary directory to put the files you downloaded.

So much this.... the amount of bullshit extension devs have to do just to write basic features expected of desktop software is insane.

DownThemAll was a treasure, as was the old version of VideoDownloadHelper. They. Just. Worked. Exactly like one would expect them too. I haven't used DownThemAll since the transition but while VideoDownloadHelper stil does what is used to do -- technically -- its functionality is so gimped now that I've resorted to using youtube-dl

Re:Mozilla’s Uncertain Future by TedDoesntTalk on Saturday August 15, 2020 @10:11AM (#24168979)
> They made ONE switch to a superior and standard extension model

No, they made TWO. The original model was the XUL-based one. Then there was the Add-on SDK:

https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Add...

THEN WebExtensions.

So some extensions had to be ported twice, within just a couple of years. This alienated a LOT of add-on developers.

Re:Mozilla’s Uncertain Future by josefx on Saturday August 15, 2020 @04:47AM (#24167181)
> They made ONE switch

How many plugins work with the new Firefox on Android?

> standard extension model

One were Google already declared that APIs used for ad blockers are considered deprecated and might be dropped at any time? With one major browser vendor being actively hostile towards a large amount of plugins that "standard" doesn't do much. It certainly doesn't guarantee portability unless Mozilla completely jumps the shark and also kills ad blockers.

Re:Mozilla’s Uncertain Future by outadoc on Saturday August 15, 2020 @07:16AM (#24168040)
Before they had to be made specifically for Firefox for Android. Once they finish implementing WebExtensions it'll be able to install any WebExtension. I'd say that's a lot better than before.

I'll add that the few extensions already available were well-picked and honestly already fulfill all my needs.

Re:Mozilla’s Uncertain Future by nicoburns on Saturday August 15, 2020 @05:20AM (#24167366)
About 8 currently. But they're still working on enabling more. And they haven't pushed the new version to the stable channels yet.
Re:Mozilla’s Uncertain Future by josefx on Saturday August 15, 2020 @05:40AM (#24167499)
For some reason I can no longer start the normal Firefox on Android, even after clearing everything and reinstalling it. So I am stuck with the beta version.
Re:Mozilla’s Uncertain Future by eitland on Saturday August 15, 2020 @07:09AM (#24168010)
> Without that Firefox would just be slow as hell, wouldn't play YouTube or Netflix videos,

OK, this is just plain wrong IMO.

Speed is a major thing for me and I never had issues with it, even with 400+ tabs. I can go as far as understanding that not everyone was as lucky as me but it seems the speed issue is given too much weight.

> and not have any extensions left because no one wants to create an extension from scratch just for Firefox.

There seems to be fewer real extensions now than before. Yes: more websites packed as extensions, less working TST, Scrapbook etc.

Re:Mozilla’s Uncertain Future by baby on Saturday August 15, 2020 @01:37PM (#24170624)
There was definitely a period were everyone (including me) was complaining about Firefox' speed.
Re:Mozilla’s Uncertain Future by dependenttypes on Saturday August 15, 2020 @06:17AM (#24167704)
> to a superior

Even now it lacks a lot of necessary APIs that the old one had - such as the ability to disable ctrl+q on linux. I would argue that only around now the new model became usable.

> Making it a more secure

In expense of usability.

> wouldn't play YouTube

It played youtube before and it would still play it without the switch.

Regardless, the old extension model was not the only power user feature which they killed (rss and panorama were two others).

Re:Mozilla’s Uncertain Future by secondcoming on Saturday August 15, 2020 @07:19AM (#24168057)
why would a web page expect to be allowed to control a user's keyboard?
Re:Mozilla’s Uncertain Future by dependenttypes on Saturday August 15, 2020 @11:29AM (#24169562)
It shouldn't, I was talking about addons.
Re:Mozilla’s Uncertain Future by luckylion on Saturday August 15, 2020 @05:34AM (#24167467)
> They made ONE switch to a superior and standard extension model, and HN loses its minds.

They did the same for Thunderbird recently. Given their approach to only provide the minimum of features and say "get an extension if you want anything more", that's an issue if you're killing those extensions.

Re:Mozilla’s Uncertain Future by dependenttypes on Saturday August 15, 2020 @06:23AM (#24167747)
They are adding openpgp support to thunderbird because enigmail will be dead soon. So much for extensibility.
Re:Mozilla’s Uncertain Future by ekianjo on Saturday August 15, 2020 @08:39AM (#24168458)
> superior and standard extension model,

Superior as in, that can do less things than XUL extensions? I am at loss, has the meaning of 'superior' changed recently?

Re:Mozilla’s Uncertain Future by marcinzm on Saturday August 15, 2020 @10:26AM (#24169097)
It can do less but won't cause your browser stability, performance and other issues. Nor will writing them require reading the Firefox source code. XUL extensions routinely hijacked random internal Firefox functions which is why many had issues being installed together. Then all of it was executed in a single context (which is why they could hijack those functions to begin with) along with the UI and web page Javascript.
Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @12:21PM (#24170017)
Those are all things they could have fixed incrementially, over time, but chose not to.
Re:Mozilla’s Uncertain Future by marcinzm on Saturday August 15, 2020 @01:16PM (#24170448)
The end result would have been the same: broken backwards compatibility. The fundamental design of the original extensions was incompatible with a modern browser model (APIs only rather than hacking internal functions, separate contexts for everything, multiple processes, etc.). They chose to do it one go rather than piecemeal. So rather than having to check every version if some functionality your extension depends on is being removed you had to rewrite it once (well twice which was a mistake on their part).
Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @04:00PM (#24171898)
It would have been gradual, and under most circumstances fixable with a bit of refactoring. Ripping the entire platform out from under people would not have produced the same result.
Re:Mozilla’s Uncertain Future by marcinzm on Saturday August 15, 2020 @05:21PM (#24172507)
In the end the people who are most knowledgeable and most involved decided a gradual change was not feasible. Armchair quarterbacking them, without very specific and detailed arguments, just feels like the Dunning–Kruger effect in action.
Re:Mozilla’s Uncertain Future by jefftk on Saturday August 15, 2020 @09:43AM (#24168797)
Superior, as in defines a standard API. A clear API means the browser maker is free to change the internals of the browser, without worrying about changing something that some extension relies on.
Re:Mozilla’s Uncertain Future by gvjddbnvdrbv on Saturday August 15, 2020 @06:09AM (#24167648)
As a power user I am aware of more than one breaking change.

They constantly mess up my attempts to automate provisioning.

Add on installation has been messed up.

Lots of my user.js suddenly gets ignored because of breaking changes.

Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @12:13PM (#24169940)
It's soo more than that. They'd destroyed all the old UI in favor of Chrome-style HTML+JS instead of platform-native XUL

They added all sorts of weird commercial initiatives to someonething that was supposed to be privacy-oriented and nonprofit

They torched an entire ecosystem of extensions so they could be more Chromelike

They put out landing pages and press releases full of weasely PR speak instead of the "mainstream engineering" vocabulary they used to use

Maybe Firefox should get in touch with the Pale Moon guys and use their code as a basis for resurrecting everything that made FIrefox great

Re:Mozilla’s Uncertain Future by dralley on Saturday August 15, 2020 @12:31PM (#24170107)
> It's soo more than that. They'd destroyed all the old UI in favor of Chrome-style HTML+JS instead of platform-native XUL

It's a browser, the entire purpose of a browser is rendering HTML+JS quickly and efficiently. XUL primitives are not, on average, faster or more "platform-native".

>They added all sorts of weird commercial initiatives to someonething that was supposed to be ... nonprofit

You understand the problem here, do you not? People complain that they're almost completely reliant on Google for revenue, and they also complain about "weird commercial initiatives" to mitigate their reliance.

>They torched an entire ecosystem of extensions so they could be more Chromelike

XUL / XPCOM had significant, tangible problems. It's not just about being "chromelike", not at all.

https://mozilla.github.io/firefox-browser-architecture/text/...

https://mozilla.github.io/firefox-browser-architecture/text/...

Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @12:40PM (#24170183)
> XUL / XPCOM had significant, tangible problems.

Significant problems that could have been fixed

> XUL primitives are not, on average, faster or more "platform-native".

At least on Windows they mapped to their native components. Sure spacing and a few other things were a little off (maybe because it mapped to GTK? I don't remember) but the look and feel then was vastly superior than the Electron-looking garbage that extensions have to do now.

> You understand the problem here, do you not? People complain that they're almost completely reliant on Google for revenue, and they also complain about "weird commercial initiatives" to mitigate their reliance.

You're not understanding me. Most folks have no problem with Pocket and whatever else. What they have a problem with is bundling it with the browser in a way that can't be removed, and then putting out a press release full of PR speak about how important and essential these extras are. These commercial iniatives were made mandatory, even when their beta versions were downloadable extensions

I'm all for Mozilla reaching out to whoever they want to partner with. But keep that shit out of the master repo. The downloadable base should be pure platform and nothing else, with extras as preinstalled, removable extensions. Essentially, the Winamp model

> https://mozilla.github.io/firefox-browser-architecture/text/....

What I see there are mostly people issues that come with not wanting to pay for the talent you need to get the job done. It looks like they had the money to do this but it feels like they spent it on admin and marketing folks instead

The XBL document mentions more systemic problem but I maintain that they could have been fixed iteratively

Re:Mozilla’s Uncertain Future by sfink on Saturday August 15, 2020 @02:07PM (#24170907)
>> XUL / XPCOM had significant, tangible problems. > Significant problems that could have been fixed

Mozilla agreed with you for a long, long time. But we eventually realized that while yes, we could continue to keep fixing those problems, that the opportunity cost was large: fixing XUL issues was taking the place of improving stuff that web pages actually use, and it would be better to not be splitting the effort both ways.

(I work for Mozilla, though mostly not on the stuff being discussed here.)

Re:Mozilla’s Uncertain Future by dralley on Saturday August 15, 2020 @01:35PM (#24170601)
>The XBL document mentions more systemic problem but I maintain that they could have been fixed iteratively ... >Significant problems that could have been fixed

It is not like the Firefox developers do not understand the value of iterative change. That was after all the basis for Project Quantum. If this were true, they would have done it.

But I'll let a Mozilla engineer explain this instead:

https://dblohm7.ca/blog/2015/08/30/on-webextensions/

https://dblohm7.ca/blog/2017/11/16/legacy-firefox-extensions...

Re:Mozilla’s Uncertain Future by baby on Saturday August 15, 2020 @01:36PM (#24170611)
it's definitely not superior seeing how tree style tab is still somewhat broken (which is the number one reason for anyone to switch to firefox)
Re:Mozilla’s Uncertain Future by KingOfCoders on Saturday August 15, 2020 @04:21AM (#24167049)
"Firefox would just be slow as hell"

Why is that?

The problem is they get into to web standards game which is driven by Google to create pressure everyone else to spend millions on the newest standards.

I don't need the newest standards, 2000 web works perfectly fine for me (except HTTPs).

Firefox is slow with many tabs open on Win10, Ryzen X3900 with 32gb of RAM (writing this from FF)

They broke exetensions several times without any benefit to users, but losing extensions on the way. One of the core features for power users dropped for nothing - well for their own fun rewriting the browser and rendering engine several times, I guess it was fun at least doing "interesting things".

Re:Mozilla’s Uncertain Future by ohgodplsno on Saturday August 15, 2020 @04:49AM (#24167195)
>well for their own fun rewriting the browser and rendering engine several times, I guess it was fun at least doing "interesting things".

Go on, install Firefox 3. Go see how absolutely _awful_ it was with multiple tabs open. How a single page would freeze the entire browser. How extensions broke XUL when the slightest thing went wrong.

Rewriting the renderer is not something done for fun. It was necessary for the to be able to do per tab isolation, as well as a not broken security model.

> Firefox is slow with many tabs open on Win10, Ryzen X3900 with 32gb of RAM (writing this from FF)

I literally have 432 tabs open at the moment I'm typing this. Firefox has automatically unloaded about 400 of those and is only eating 3GB of RAM. Check your custom config if you have any, because you certainly have something wrong. Win10, Ryzen 1600X and 16GB.

Re:Mozilla’s Uncertain Future by KingOfCoders on Saturday August 15, 2020 @10:00AM (#24168898)
I'm using FF since Mosaic days and it was always slow. But how come if everything was bad back then, it isn't blazing fast with 100x faster hardware from my SGI days and several rewrites?
Re:Mozilla’s Uncertain Future by orra on Saturday August 15, 2020 @04:39AM (#24167142)
The old extensions were synchronous and ran in the GUI thread. Running firefox with extensions on a HDD would freeze all the time for me, before electrolysis.

There also was not a good security model.

WebExtensions fixed these problems.

Re:Mozilla’s Uncertain Future by badsectoracula on Saturday August 15, 2020 @09:23AM (#24168677)
> There also was not a good security model.

What security model? Pretty much every WebExtension i've come across asks for practically everything and even Firefox's own addon page tells you to only install extensions you trust. At that point if you trust the extension source why bother with the security model in the first place? You already trust the extension developer to not break anything.

Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @12:24PM (#24170049)
The one issue there is with developers that sell out their extensions to shady people. While I love the XUL era way more than this current trash, the security model with XUL would have done nothing to limit the blast radius and the update system would potentially install it silently

That said there used to be a human review system in place for extensions. I'm not sure if they do that any more

Re:Mozilla’s Uncertain Future by badsectoracula on Monday August 17, 2020 @07:05AM (#24186046)
That is an issue with the current system too, sure an extension isn't able to look at arbitrary files in your system, but it still is able to look at your bank site, passwords, etc and can still do a ton of damage.

Web extensions aren't safe by default, you shouldn't trust them any more than any arbitrary EXE file.

Re:Mozilla’s Uncertain Future by asddubs on Saturday August 15, 2020 @04:55AM (#24167227)
I have to say, even though webextensions are clearly better and the way forward, i still kind of miss the old tamper data extension. ZAP just ain't as convenient to start up
Re:Mozilla’s Uncertain Future by pitay on Saturday August 15, 2020 @05:40AM (#24167495)
Strangely I had the opposite thing happen, there were freezes after electrolysis, and it ran super fine before.

The freezes were the network, where if anything was required from the network the page would just pause for many seconds, this happened on all tabs, and after the pause they would all load/come back at the same time. Something was holding up all the network activity in Firefox.

Also there was a large amount of memory used, actually made it better by changing cache settings, the biggest being turning off the disk cache, for some reason that lowered the memory usage drastically.

But as far as I can tell the network pausing issue has mostly gone away now in the last year or so.

Re:Mozilla’s Uncertain Future by joepie91_ on Saturday August 15, 2020 @04:44AM (#24167171)
> Why is that?

Because Firefox's "powerful extension model" basically constituted direct access to its internals, which prevented the Firefox developers from making the architectural improvements that were so sorely needed to make it performant.

> Firefox is slow with many tabs open on Win10, Ryzen X3900 with 32gb of RAM (writing this from FF)

Admittedly I'm on Linux, but I currently have approximately 7800 tabs open (no, that is not a typo). Firefox is a little laggy in its UI, but Chrome has never even managed to have more than a few hundred open without becoming unusable, so I'd say that Firefox is doing fine here.

Interestingly, the slowdown actually seems to originate from rendering the tab bar, not from the tabs themselves.

Re:Mozilla’s Uncertain Future by anoncake on Saturday August 15, 2020 @09:16AM (#24168640)
> Because Firefox's "powerful extension model" basically constituted direct access to its internals, which prevented the Firefox developers from making the architectural improvements that were so sorely needed to make it performant.

Not necessarily. They could have added and recommended stable APIs that solve most use cases while still allowing extension developers direct access to the internals at the cost of having to update the extension more frequently.

Re:Mozilla’s Uncertain Future by xxs on Saturday August 15, 2020 @07:47AM (#24168176)
I wonder how you define 'open', if they are just URLs and perhaps content on disk (+persisted javascript state) - they are not open/live. What's the benefit compared to fetching the contents off the web and rendering them anew?

Personally, I use different windows with several tabs open related to each other, when I done with the matter I close the window.

Re:Mozilla’s Uncertain Future by KingOfCoders on Saturday August 15, 2020 @09:57AM (#24168884)
What extension do you use for 7800 tabs? Do you search for the tab if you want to go for one?
Re:Mozilla’s Uncertain Future by solstice on Saturday August 15, 2020 @06:55AM (#24167932)
Not judging you, but why do you have so many tabs open?
Re:Mozilla’s Uncertain Future by orthoxerox on Saturday August 15, 2020 @03:48PM (#24171768)
I also have no idea what they do with all these tabs. I routinely close my tabs at the end of the day.
Re:Mozilla’s Uncertain Future by harshitaneja on Saturday August 15, 2020 @04:54AM (#24167223)
2000 web may work well for you but there are many of us who desire and even need the newer web standards. I am glad we are extending our applications with open standards rather than closed implementation-specific solutions of the past.

I think we all really under-appreciate the marvel that is our current web. We run large complex distributed applications with remote frontends on our sandboxed environments. For most of the things I don't have to install apps anymore, which means as a linux user I finally get to access a similar ecosystem as everyone else. From running businesses to having fun to tinkering around, everything happens in this single window in our computers.

I have my concerns about google as well but I am glad mozilla and google have led to the interesting new web that we have today.

Re:Mozilla’s Uncertain Future by tester756 on Saturday August 15, 2020 @04:36AM (#24167132)
>Firefox is slow with many tabs open on Win10, Ryzen X3900 with 32gb of RAM (writing this from FF)

How many is many?

I'm using up to 10-20 and it never felt slow on worse setup.

Re:Mozilla’s Uncertain Future by eitland on Saturday August 15, 2020 @07:15AM (#24168032)
10-20 are so few you can get away with it in Chrome or even old IE.

Many is somewhere north of 200. Many of us are routinely on 400 and more.

As for why, I at least consider the computer an extension of my mind. What it remember, I don't have to.

Edit: Chrome can handle way more than that, it just becomes very tedious when you cannot see the tabs. Also I don't know if omnibar can search for open tabs like awesomebar?

Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @12:26PM (#24170064)
FFS, learn to organize "your mind" then. 400+ tabs tells me you need to be using bookmarks
Re:Mozilla’s Uncertain Future by BugWatch on Saturday August 15, 2020 @01:43PM (#24170674)
I have to disagree. In my case, bookmarks are the place where "tabs" go to die. I use Tree Style Tab addon, and tabs (mostly self-)organize as I surf, do research on different topics and whatnot, and I jump in with a window title changing addon or grouping parent tab. I cannot even imagine using a browser without it. But bookmarks do not preserve any of that relational data. Session managers are also luckluster solution at best, because merging a few tabs, a tree or window with existing session is clunky at best. After many years of frustration, I have started working on my own tab syncher/organizer.

Bookmarks are only the coldest of storage for me, with exception of bookmarks bar where I place often accessed web sites.

Re:Mozilla’s Uncertain Future by eitland on Saturday August 15, 2020 @02:04PM (#24170883)
"Ahhh, finally I got you bug: I saw this just the other day when I looked at x" works so much better when x is an organized as a tree of tabs, in the memory of my browser, a short scroll and a click away instead of having to hunt through bookmarks reloading all of them in hope of figuring out which one it was.

At least with the work I do it isn't alway obvious what is going to be useful or not. But while I don't have a photographic memory (quite the contrary) I'm often able to figure out approximately where to look and also able to find it there.

I'd even recommend you try it. If it works for a simple farmer turned engineer like me, think what it could do for a smart person like you! ;-)

Re:Mozilla’s Uncertain Future by tomc1985 on Saturday August 15, 2020 @04:37PM (#24172171)
The bookmark menu supports the same hierarchical organization, and since you're pretty much using so many tabs as bookmarks anyway, I don't see much of a distinction. Deleting bookmarks is a bit more fiddly than closing tabs, but in my mind that is a good thing as I find myself accidentally closing tabs all the time. And I bet the "Close Other Tabs" option probably scares the crap out of you

Tabs are supposed to be short-lived, ephemeral things. Bookmarks have the functionality you want

Re:Mozilla’s Uncertain Future by eitland on Sunday August 16, 2020 @01:47AM (#24175531)
I think you are kind of rude both in that you suggest you absolutely know better than me, and also in how you present your opinions.

I suggest you take a step back and reconsider both:

- computers as bicycles for the mind. If it can do so much for me, think what you could achieve!

- how you interact with others.

PS: no, "close other tabs" doesn't scare me. If I have to close down something I don't feel I have finished yet I can select that subtree and export it to the clipboard as a nested markdown list which I paste into Joplin where it is searchable.

Also if I accidentally close down something I can just press ctrl - shift - t the required number of times, alternatively ctrl - shift - n if a whole window has been closed.

Re:Mozilla’s Uncertain Future by dependenttypes on Saturday August 15, 2020 @06:26AM (#24167769)
I would consider 500+ as "many". 10-20 would be considered as "very few".
Re:Mozilla’s Uncertain Future by KingOfCoders on Saturday August 15, 2020 @09:56AM (#24168873)
I currently have around 120 open in "Simple Tab Groups". But this can go up to 200+
Re:Mozilla’s Uncertain Future by andybak on Saturday August 15, 2020 @07:52AM (#24168195)
> I don't need the newest standards, 2000 web works perfectly fine for me

How about layouts being broken because (funnily enough) web developers are desperate to use features such as grids and flexbox that make their jobs less painfully awful?

Presuming you're a developer - surely you can sympathise with the desire to get people to upgrade their browsers so that webdev's lives are made more pleasant?

Re:Mozilla’s Uncertain Future by setzer22 on Saturday August 15, 2020 @08:36AM (#24168438)
I, for one, think the HTML API (as in, the interface presented to the programmer, not talking about any other API meaning here) couldn't be worse.

How many attributes do you need to enable to place two pictures side by side in vanilla CSS? Is that composable, would the same set of flags work for two paragraphs? What about two tables?

HTML/CSS was never designed for the web we have ended up with, and I don't see how flexbox and any newer standard is making developers lives anything but miserable.

Re:Mozilla’s Uncertain Future by remexre on Saturday August 15, 2020 @01:16PM (#24170438)
I believe flexbox does actually work for those cases, assuming you set the images/paragraphs/tables to be block elements (or wrap them in divs)?

Flexbox and Grid seem to me like recognition that the existing CSS primitives were designed for laying out documents, and don't fit well for creating UIs.

Re:Mozilla’s Uncertain Future by squarefoot on Saturday August 15, 2020 @11:37AM (#24169618)
I think Firefox lost users to Chrome mainly because Google advertises their product constantly.

What you point out about trying to imitate Chrome is right though; when they dumbed down the very complete and functional settings window into an almost empty HTML page that forced to resort to about:config to do anything non trivial, or when they literally copied the terrible Chrome main window structure, I literally wanted to puke. I'm not sure however this is the reason why normal users distanced from the product. Firefox back then was the alternative to Internet Explorer and its load of security and privacy problems, so it started in a context where a good number of users actually wanted to switch to a different browser, despite some lock-ins such as Active-X and the like, I believe even Opera had some well deserved success at a moment for that reason, but none of them could compete anymore when the new kid in the block was a strongly and pervasively advertised product like Chrome. Firefox today is faster and more user privacy friendly than Chrome; to me if most people don't use it is simply because they don't know. Small personal example: of the many people I installed it, the number of those that went back to Chrome is a single digit percentage, which should suggest they didn't choose Chrome initially, but rather they didn't know about the alternatives.

Now it's the time for all Firefox users to tell others that they chose Firefox, and why, then for Mozilla to invest some damn money in advertising!

Re:Mozilla’s Uncertain Future by TimSchumann on Saturday August 15, 2020 @03:42AM (#24166842)
I find it hard to disagree with this sentiment.

I don't use firefox as my main browser because it's better than Chrome, I use it because it's not google.

Re:Mozilla’s Uncertain Future by lrem on Saturday August 15, 2020 @04:11AM (#24167003)
Seeing Google from the inside, I have way more trust in it than the general public. But I do use Firefox as my personal browser because I like what they're doing with the tech stack. Having everyone just slap their logo on Chromium sounds like a way towards eventual stagnation.
Re:Mozilla’s Uncertain Future by glenstein on Saturday August 15, 2020 @05:34PM (#24172619)
This is the reason why I was initially excited about, and then disenchanted with Vivaldi. I initially had the impression that they weren't going to use Chromium, and that their return to Opera's roots meant returning to the spirit of innovation that made Opera so compelling back in the day (I will never stop singing the praises of Opera Unite). But then I learned that Vivaldi, too, would be based on Chromium.
Re:Mozilla’s Uncertain Future by bickeringyokel on Saturday August 15, 2020 @03:49AM (#24166880)
I find I am not missing anything in terms of features or stability since the quantum engine except perhaps bookmark management being a bit clunky.

If you truly prefer chrome why not use a chromium browser that is not Google? (Brave for example)

Re:Mozilla’s Uncertain Future by TimSchumann on Saturday August 15, 2020 @03:53AM (#24166902)
I question the longevity and/or motives of institutions maintaining any of those builds other than possibly Microsoft.

And believe me, if you would have asked me if trusting Microsoft was the safe bet 20 years ago, I would have said you were nuts. But here we are.

Re:Mozilla’s Uncertain Future by riffraff on Saturday August 15, 2020 @04:47AM (#24167188)
I understand questioning the motives, but does the longevity matter? I have a ton of bookmarks and some extensions, but those carry over easily across chrome variations. If Brave died next year you could switch back to chromium relatively easily, I think.

I guess, I may be missing something, and would like to know what.

Re:Mozilla’s Uncertain Future by KingOfCoders on Saturday August 15, 2020 @04:36AM (#24167130)
" I use it because it's not google. "

Me too.

Re:Mozilla’s Uncertain Future by robbrown451 on Saturday August 15, 2020 @06:11AM (#24167668)
That's a tough sell for the vast majority of non-HN users.
Re:Mozilla’s Uncertain Future by alcoholic_byte on Saturday August 15, 2020 @10:34AM (#24169155)
Try the privacy sales pitch. And for mobile there is Firefox-Focus. Yes you have to do a lot of typing, but hell do I not miss targeted advertisement in browser.
Re:Mozilla’s Uncertain Future by giancarlostoro on Saturday August 15, 2020 @12:10PM (#24169908)
It's really a shame, and I've mentioned this before. If Mozilla sells a 'Developer' version of Firefox that is technically fully open source, but the idea is that it will directly support Firefox development, I will pay, you can add tiers, a VPN (since they're going to offer this anyway) and other goodies (maybe I can finally have a cool @firefox / mozmail.com / foxmail.com email or whatever) and I would probably subscribe to pay for higher tiers if it brings me other benefits, the email bit I mention because they do already provide an email client, it's a shame they never produced their own email service to subsidize their efforts elsewhere.

Mind you they already have Firefox Developer edition, they can keep it free and add a Firefox Professional Developer Edition that guarantees funds go to better funding Firefox development and I will be one of the first to pay for it, if it's got a monthly subscription or yearly. No "discount" tactics either, please, it makes no sense for someone trying to maintain a lot of non-profit open source projects.

Re:Mozilla’s Uncertain Future by MattGaiser on Saturday August 15, 2020 @03:49AM (#24166883)
The challenge with not competing with Chrome is that websites are now mostly developed with Chrome as the dev-tool.

Even large companies are just optimizing for that one browser:

https://thenextweb.com/dd/2017/11/28/please-build-websites-w...

How many users are going to be willing to put up with stuff not working until they switch?

Re:Mozilla’s Uncertain Future by causality0 on Saturday August 15, 2020 @03:55AM (#24166918)
Functioning like Chrome in rendering and page features doesn't mean Firefox has to behave like Chrome in the UX. For example, why gut the ability of people to skin and customize their browser as they see fit? Why is Mozilla involved in a running battle against users who want the tabs below the address bar? Why entirely prevent us from sideloading extensions instead of letting us turn the ability on and off?
Re:Mozilla’s Uncertain Future by afiori on Saturday August 15, 2020 @04:02AM (#24166955)
I guess that for the first two the answer is in part managing complexity
Re:Mozilla’s Uncertain Future by asddubs on Saturday August 15, 2020 @04:53AM (#24167215)
and the last one is to reduce attack vectors
Re:Mozilla’s Uncertain Future by dependenttypes on Saturday August 15, 2020 @06:25AM (#24167757)
Ah yes, the good old walled garden approach.

Not very "open", is it?

Re:Mozilla’s Uncertain Future by asddubs on Saturday August 15, 2020 @06:59AM (#24167964)
i mean I don't like it either, but I do believe them in this instance that it's mostly in service of not letting installers just sneak in a toolbar
Re:Mozilla’s Uncertain Future by dependenttypes on Saturday August 15, 2020 @11:29AM (#24169557)
I think that this is misguided. If a malicious installer sneaks in toolbars it can also install a keylogger/send all of your data to a server/install a firefox fork with the toolbar preinstalled/etc.

If anything this kind of thing only hurts the users that know what they are doing (such as someone wanting to install a 3rd party addon or someone wanting to install addons via nix).

Re:Mozilla’s Uncertain Future by notriddle on Saturday August 15, 2020 @05:10PM (#24172422)
> If a malicious installer sneaks in toolbars it can also install a keylogger/send all of your data to a server/install a firefox fork with the toolbar preinstalled/etc.

If it's totally rogue malware, sure.

The toolbars, on the other hand, were coming from companies like Oracle that operated entirely within the bounds of the law.

Re:Mozilla’s Uncertain Future by dependenttypes on Monday August 17, 2020 @09:23PM (#24194359)
Installing a firefox fork is also within the bounds of the law.
Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @04:06AM (#24166981)
The anti-IE generation is mostly to blame for that, they ended up adopting the behaviours they criticized so much.
Re:Mozilla’s Uncertain Future by toyg on Saturday August 15, 2020 @04:49AM (#24167194)
It is indeed sad how people who hated IE so much have now enabled the next IE not once but twice (Chrome on the desktop, Safari on mobile).
Re:Mozilla’s Uncertain Future by MattGaiser on Saturday August 15, 2020 @04:21AM (#24167048)
IE made life miserable for developers. I am not sure we would have cared if it were not moribund.
Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @06:48AM (#24167905)
Nope it was pretty great actually, then Microsoft thought they had won the war.
Re:Mozilla’s Uncertain Future by jefftk on Saturday August 15, 2020 @09:18AM (#24168648)
Initially, IE6 was much better than the competition. But it was still buggy, and had some very weird rendering behavior. Over time, other browsers became much less buggy, but IE6 was still around. That's how IE6 came to be viewed, in retrospect, as a very buggy browser.
Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @10:56AM (#24169314)
Should we have a look at Chrome's bug database?
Re:Mozilla’s Uncertain Future by jefftk on Saturday August 15, 2020 @11:50AM (#24169727)
Chrome was the first browser to adopt an evergreen model, where updates were installed automatically. While Chrome (and Firefox, once they adopted this model) have had many bugs over the years, when they fix a bug everyone gets the fix. The problem with IE6 (and later, up until Edge) was that bugs were here permanently: something that web developers needed to work around for as long as anyone was still using that browser.
Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @11:58AM (#24169796)
Should we go through all open tickets that are open since 2013? Or start even earlier with the "forced closed" ones?
Re:Mozilla’s Uncertain Future by jefftk on Saturday August 15, 2020 @01:24PM (#24170506)
IE6 had major compatibility bugs that were never going to be fixed. For example:

* It considered width to include border and padding, when the spec and other browsers did not: https://www.jefftk.com/p/the-revenge-of-the-ie-box-model

* Floated block elements would get their margins doubled, so people would typically use padding instead.

* Its implementation of height was more like min-height.

While I'm sure Firefox and Chrome have open bugs that are older than that, I'd expect them to be much less important than these critical misinterpretations of CSS.

Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @01:40PM (#24170655)
Well, I can track down examples of similar critical bugs for Chrome, but then again, I guess it would just move the goal posts to another defence round for Chrome.
Re:Mozilla’s Uncertain Future by jefftk on Saturday August 15, 2020 @01:54PM (#24170780)
You think Chrome, Firefox, Edge, or Safari (the main evergreen browsers) have bugs that have been open for years and are as critical as considering an element's width to include its border and padding? This misinterpretation of the CSS specification was something that essentially all front-end developers had to work around for 10+ years!
Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @03:52PM (#24171803)
Yes I think so, all of them have bugs that web developers have to work around, again should we look at Chrome's bug database or maybe AdWords has a better source of information for such workarounds?
Re:Mozilla’s Uncertain Future by jefftk on Saturday August 15, 2020 @04:38PM (#24172178)
If you want to point to an example bug, I think that would help me understand your point, yes.

(To give a sense a sense of the scale I think we're talking about, this would be a bug that, say, more than half of web developers have to understand and work around in a typical month)

Re:Mozilla’s Uncertain Future by pjmlp on Sunday August 16, 2020 @01:32AM (#24175457)
My point it that you are tainted by your employer, so this discussion is worthless, no matter what I come up with.
Re:Mozilla’s Uncertain Future by ohgodplsno on Saturday August 15, 2020 @04:52AM (#24167213)
Whereas Chrome makes life miserable for users not using Chrome, because of the sheer amount of non-standard, Chrome-only features used in current webdev.
Re:Mozilla’s Uncertain Future by harshitaneja on Saturday August 15, 2020 @05:01AM (#24167252)
Which non-standard features?
Re:Mozilla’s Uncertain Future by ohgodplsno on Saturday August 15, 2020 @05:28AM (#24167416)
Using google properties is a bit of an easy jab, but:

Youtube using polymer/shadowdomv0 and absolutely destroying performance on Firefox is a an easy example. Google Earth used non-standard APIs.

Otherwise, have a quick search for "non-standard" on MDN, and see how many of those Chrome implements.

Re:Mozilla’s Uncertain Future by eyko on Saturday August 15, 2020 @07:06AM (#24167996)
But both of those are Google products. Yet here we are in a thread blaming an entire generation of web creators and users.
Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @12:11PM (#24169914)
Ah, so only when Microsoft does it is bad, but when that generation worships Google for doing the same it is suddenly alright.
Re:Mozilla’s Uncertain Future by xxs on Saturday August 15, 2020 @04:06AM (#24166976)
Make better and paid/subscription based(!) dev tools, instead screwing the UI and disabling add-ons. People are buying jetbrains products even though free ones exist.

I do use firefox but all the auto-update features are off on desktop. On mobile I am/will be stuck with 68 forever, I suppose as well.

Re:Mozilla’s Uncertain Future by usrusr on Saturday August 15, 2020 @08:07AM (#24168289)
Perhaps FF developer edition was meant to test the waters for this approach? Do web people actually use that? I never got to the point of making it part of my process, but I'm not doing enough web to really have a process.

In any case, a dev browser can only be relevant if it's representative of end user browsers. The history of browser wars has shown that a superior dev experience can be a decisive factor in winning users, but it can never be more than a supporting role.

These days a far more plausible dev level monetization angle would be Mozilla's unique position as the origin of Rust. Spin out a Rust subsidiary that sells service and perhaps also some premium tooling/SaaS in the open market while doing work on Rust/Servo/FF for a nominal fee that allows both sides to keep the lights on.

But that (just like paid browser dev tools) would be B2B and apparently Mozilla Corp completely fails to see itself as a B2B actor outside of consumer eyeballs deals like the Google deal and the increasingly outbrainy start tab fillers.

But failure to go that way is hardly surprising. Where would the business skillset come from when the entire organizion outside the tech teams has more in common with the great money furnaces of Wikimedia than with anything else?

The only way I can see for that kind of transition to go well would be some form of merger/acquisition with someone already existing in those fields (consultancy and/or tooling). "you take the engineers, we'll be buying services". But the successful ones would be very reluctant to suddenly load themselves with the entirety of Rust. It would probably take someone owner-managed who brought a decent amount of idealism into the equation. Total number of candidates might amount to zero.

Re:Mozilla’s Uncertain Future by TimSchumann on Saturday August 15, 2020 @03:56AM (#24166922)
This is the main thing I’m concerned with. Instead of adhering to an open standard, everything becoming ‘whatever google says goes’.
Re:Mozilla’s Uncertain Future by cotillion on Saturday August 15, 2020 @04:01AM (#24166947)
The Firefox bug report for a websocket message inspector was opened 7 years ago. It took 6 years before it got implemented.

Its no wonder they lost marketshare among developers.

Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @04:07AM (#24166985)
I can find similar examples in Chrome, yet that doesn't detain some devs to worship it.
Re:Mozilla’s Uncertain Future by MattGaiser on Saturday August 15, 2020 @04:17AM (#24167032)
Yes, but Chrome is considered the default. If something doesn't work in Chrome, I will get in trouble with my boss for implementing it.

If something doesn't work with Firefox, we tell the users to use Chrome.

Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @06:48AM (#24167902)
So just like IE 6, some things never change in spite people telling otherwise.
Re:Mozilla’s Uncertain Future by TimSchumann on Saturday August 15, 2020 @04:03AM (#24166961)
Agree with this sentiment 100% - it’s not better, it’s just less evil.
Re:Mozilla’s Uncertain Future by xg15 on Saturday August 15, 2020 @10:38AM (#24169184)
I don't know if that was really Mozilla's fault or that Google was always in a position where they could force Mozilla's hand.

When Firefox was at its absolute maximum market-share, Google was already the "start page of the internet" thanks to its search page. They used this and other marketing/bundling strategies (which were possible thanks to Google's resources) to aggressively grow Chrome's market share at an unprecedented rate. Compare Firefox' incredibly heroic battle against IE which, after a decade of advocacy, archived an unbelievably-seeming 30% global market share - with the rise of Chrome, which went from 0% to 50% in a few years and completely obliterated IE. [1]

Sorry, but that was never an even playing field.

It's amazing what they did manage to archive in their position - but with Google dominating both the browser and the way web sites are discovered, they have far more leverage to influence web standards than Mozilla has. I think Mozilla's choice was one of "copy Chrome and keep at least some amount of influence on the web" or "do your own thing and become incompatible with the web that actually exists".

[1] https://gs.statcounter.com/browser-market-share

Re:Mozilla’s Uncertain Future by ukyrgf on Saturday August 15, 2020 @02:28PM (#24171094)
I don't remember Google throwing any marketing at being the start page of the internet. That was a Reddit campaign trying to get users to switch from Digg.
Re:Mozilla’s Uncertain Future by cel1ne on Saturday August 15, 2020 @03:49AM (#24166881)
I don't think so, i switched to Firefox about two years ago, after the major upgrades, and I think it's way snappier, faster and more usable than chrome.
Re:Mozilla’s Uncertain Future by Certhas on Saturday August 15, 2020 @06:04AM (#24167620)
Pretty much every Firefox discussion on Hacker news you have commenters that say they just can't stand Firefox because it's 10ms slower than Chrome. Google also has been advertising Chrome heavily for the last ten years. And there was a time when Firefox was undeniably significantly behind on performance.
Re:Mozilla’s Uncertain Future by jansan on Saturday August 15, 2020 @09:54AM (#24168857)
On our Javascript heavy app Chrome is still about twice as fast as Firefox. Admittedly it is not your average app, but I cannot confirm claims that Firefox is almost as fast as Chrome.
Re:Mozilla’s Uncertain Future by matsemann on Saturday August 15, 2020 @10:01AM (#24168912)
How much is that biased because everything has been optimized to Chrome? From frameworks to your implementation.
Re:Mozilla’s Uncertain Future by ulfw on Saturday August 15, 2020 @03:52AM (#24166900)
Who cares about the version number?

Come on. People don‘t pick a browser based on a too high or too low version number.

Re:Mozilla’s Uncertain Future by causality0 on Saturday August 15, 2020 @03:58AM (#24166928)
Exactly my point. Mozilla used a rational numbering scheme where the larger the change, the larger the increment, with full integers being reserved for major changes. Then Chrome started changing its integer every few weeks and Firefox upended its own scheme to keep from looking unfashionable.
Re:Mozilla’s Uncertain Future by ansible on Saturday August 15, 2020 @04:13AM (#24167014)
Between auto-updates and the numbers changing very often, I'm not even slightly aware of the current version numbers for Chrome or Firefox.
Re:Mozilla’s Uncertain Future by forgotpwd16 on Saturday August 15, 2020 @05:30AM (#24167431)
For a rolling-release model like this a scheme could include the date released, e.g. Firefox 20.07.x which is also used by Linux distros. Right now version numbers are pretty useless.
Re:Mozilla’s Uncertain Future by gspr on Saturday August 15, 2020 @07:12AM (#24168019)
Version numbers aren't useless. It's just that there's an insane fad going around that only the latest iteration of something is suppose to be used.
Re:Mozilla’s Uncertain Future by slim on Saturday August 15, 2020 @07:13AM (#24168027)
firefox lost it's market share because chrome was a better, faster, more complete browser. Mozilla didn't need to develop any strategy other than building and even better browser. So they tactically designed a safer language, then used it to build a better browser. It was working as planned, but they just abandoned it. Now they don't have a better browser and I wonder if they'll ever have one.
Re:Mozilla’s Uncertain Future by alcoholic_byte on Saturday August 15, 2020 @10:40AM (#24169203)
No. Bigger marketing-budget and better positioning in reaching users. If they use google with a non-Chrome browser they will be prompted to install Chrome because it is better. Some people might have just installed it so Alphabet would stop nagging them. Youtube supported some old deprecated protocol that only Chrome still supported so the users perceived youtube as performing better more reliable on Chrome, and it also gave Alphabet an excuse to say:" This does not happen with Chrome". Slyly withholding the information that Alphabet created this unpleasent user-experience in the first place.

So that smells of deceit, and manipulation to me.

Thus, even if it were true that Chrome is more performant than any other browser, I would not put my trust and security in a company resolved to use these types of actions.

//Edit

Just because I mentioned the Youtube thing twice already. In case you want to have a source: here it is https://www.zdnet.com/article/former-mozilla-exec-google-has...

// Edit 2 Well I just found out that Chrome is dropping/has dropped Certificate Pinning. How is that for improvement of the security of you user-base? FF still supports it.

//Edit 3 There was also a paper trending on HN on how QUIC aka HTTP2 threatens a user's privacy. The design-decision was explained with performance in the paper; I can get that talking about a protocol concerned with speeding up the internet, but coming from a company monetizing surveilance and targeted advertisement, is very disquieting.

Re:Mozilla’s Uncertain Future by nikitaga on Saturday August 15, 2020 @03:50AM (#24166888)
Lack of good built-in RSS reader is puzzling. Could have been their way into offering paid web services as the cross platform browser is so perfectly positioned for this feature.
Re:Mozilla’s Uncertain Future by craftinator on Saturday August 15, 2020 @03:52PM (#24171808)
Sometimes, a group makes no poor decisions, or no none that actually matter, but their goals are overcome by events, and they fail. It's not about what Mozilla did, it's about what Google did; Firefox is simply not going to win against Chrome in terms of marketshare. Of course they can still win in terms of making their browser more awesome for the people who actually use it!
Re:Mozilla’s Uncertain Future by kanox on Saturday August 15, 2020 @04:14AM (#24167020)
> constant deprecation of power features and customizability

Can you be more specific?

Advanced customization is provided by extensions and they're as well supported as ever.

Re:Mozilla’s Uncertain Future by gvjddbnvdrbv on Saturday August 15, 2020 @06:13AM (#24167676)
They really are not. Even Mozilla would not make that claim.
Re:Mozilla’s Uncertain Future by gvjddbnvdrbv on Saturday August 15, 2020 @11:28AM (#24169544)
So would anyone care to explain how vimperiator style customization is possible with webextensions? Newer Firefox explicitly does not support that level of customization.
Re:Mozilla’s Uncertain Future by remexre on Saturday August 15, 2020 @01:18PM (#24170471)
Never used Vimperator, but I'm happily typing this message in an embedded Vim using SurfingKeys on Firefox 97.
Re:Mozilla’s Uncertain Future by gvjddbnvdrbv on Saturday August 15, 2020 @01:25PM (#24170518)
Yes I also use the various attempts at vim emulation in the newer Firefox versions. The attempts are commendable given the limitations of the APIs. None of them are anywhere near as powerful in terms of vim like behaviour. If you never used any of the really powerful old style extensions you have no point of comparison.

But this is irrelevant. Previously extensions could do anything to alter Firefox. Webextensions are deliberately limited in scope - this is explicitly stated by the Firefox developers. So to say extensions as well supported as ever is factually wrong. The support is much more limited now.

Re:Mozilla’s Uncertain Future by causality0 on Monday August 17, 2020 @10:37PM (#24194723)
It's like going from a pad and paper to a typewriter. Sure, you can write much faster, more precisely, and everybody to the same standards, but you're fucked if what you wanted to do was draw a spaceship. Then there's always the apologists who come in to say that their ASCII-art spaceships are basically fulfilling the same function of the ones you used to draw and you should stop complaining.
Re:Mozilla’s Uncertain Future by antisthenes on Saturday August 15, 2020 @12:05PM (#24169865)
I can't speak for the other 25%, but this is certainly true for me.

I stopped using the official Firefox when they decided to throw away the entire plug-in ecosystem and moved to Quantum or whatever. After they did, it's been a long, but very stable slide down in power user functionality and what made it Firefox.

Re:Mozilla’s Uncertain Future by Krasnol on Saturday August 15, 2020 @08:24AM (#24168378)
As one of those conservatives who always whined about major changes:

Nah, that's not the moment of doom. The moment of doom came when google chose to spread their browser bundled with freeware and people all around ended up just having it as their major browser. Many not even knowing how that happened because they never remove the check marks on the installers. I'm still pissed that people where I installed Firefox now use Chrome as their main browser without having even realised when that changed....I wish there would be a way to block just google/Chrome installers.

Most of the people don't know/care about where Chrome comes from or that it's good to un-google or whatever. It's just a minority caring about this. This minority is not relevant to the overwhelming dominance of google.

Re:Mozilla’s Uncertain Future by blablabla123 on Sunday August 16, 2020 @02:12PM (#24179870)
> Firefox built its userbase by being different than the dominant browser, then decided the only way to not die was to be exactly like the dominant browser except with less icky behind-the-scenes privacy behavior.

Yes, that's also were Mozilla lost me. Also since last year's questionable privacy problems, I really see no point in continuing to use Firefox. Just going for maximum performance/best integration which is Safari.

For sure alternative implementations will come, Kosmonaut looks promising. Actually KHTML/Konqueror which Webkit is based on also came out of nowhere, when the Web standards where already considered sufficiently complex for nobody to do a new implementation. So I think this is fertile ground for new efforts...

Re:Mozilla’s Uncertain Future by takeda on Saturday August 15, 2020 @04:16PM (#24172004)
Agree the same thing started with Opera, previously they were known from inventing many features (some of them actually Chrome copied when it first appeared). Once Chrome started gaining traction they started be the ones that were copying Chrome. Ultimately dropping the Presto engine and becoming just another skin for Chrome. I didn't use Opera and later Firefox to get Chrome experience.
Re:Mozilla’s Uncertain Future by ptx on Saturday August 15, 2020 @05:17AM (#24167346)
> Firefox built its userbase by being different than the dominant browser

To be fair, part of what distinguished Firefox from the original Mozilla browser was that it was more similar to Internet Explorer, e.g. supporting alt+D to focus the location field and that kind of thing. But I agree that becoming too much like Chrome is a bad idea - if I wanted Chrome, I would use Chrome.

Re:Mozilla’s Uncertain Future by slightwinder on Saturday August 15, 2020 @10:09AM (#24168961)
> Firefox built its userbase by being different than the dominant browser

Not really. firefox rose tu domination as bland copy of the Internet Explorer, the dominating Browser that time. They also added parts of their own like tabs and addons, but that were just gadgets for those who knew about them.

> The 25% of internet users who wanted what Firefox offered ten years ago still want the same thing now,

What 25%? Addons are hardly used by anyone, except Adblockers. Even the most well known addons are only used by around 1-2% of the users. Adblockers are more popular, but even they seem to stuck by just 20 or 30% of firefox-users.

Re:Mozilla’s Uncertain Future by afiori on Saturday August 15, 2020 @04:06AM (#24166974)
what was 25% ten years ago is closer to 5% now
Re:Mozilla’s Uncertain Future by fastball on Saturday August 15, 2020 @05:01AM (#24167249)
I don't use FF because I still find SpiderMonkey (its JS engine) to be slower than V8.
Re:Mozilla’s Uncertain Future by alcoholic_byte on Saturday August 15, 2020 @10:51AM (#24169287)
Firstly, the question of browser superiority and choice is not just about speed. You wouldn't want to choose an operation procedure A) over B) simply because A is faster as A has a mortality rate 30%higher that B. Secondly, the web is not high-end-gaming so a few ms more or less don't really matter IMHO. Also note that Alphabet might slow their service down deliberately, because you are not using their browser. Lastly, to finish off with a strong argument, I want you to look at https://arewefastyet.com/win10/overview?numDays=60 . It always depends on the benchmark and circumstances, as I havn't checked other OSs on that site.
Re:Mozilla’s Uncertain Future by MaxBarraclough on Saturday August 15, 2020 @05:25PM (#24172543)
You mean you find the browser to be slower? There's more to a browser than its JavaScript engine. Firefox and Chrome also use entirely different rendering engines.

As for which browser really is faster, it depends on the workload. Someone already linked to https://areWeFastYet.com/

Re:Mozilla’s Uncertain Future by john4534243 on Sunday August 16, 2020 @08:51AM (#24177330)
The future of Rust language from Mozilla is also uncertain.
Re:Mozilla’s Uncertain Future by alcoholic_byte on Saturday August 15, 2020 @10:27AM (#24169099)
Google entered the game later. So according to your logic one should always drop dead the moment s.o. else enters the game.

Besides, without having read all responses to your post, FF is different, or do you think Alphabet would condone a browser that has container tabs and disables a lot of advertisement/tracking out of the box.

Also offering what I had 10years ago, means not being able to to implement new features as quickly, it stagnates development;and on top of that, it will mean less innovation, so you could turn around, crying foul, and say that not enough has been done to be innovative. In my opinion, it is a void argument, a friend to all is a friend to none so to speak.

And let's not forget, Google/Alphabet had Chrome support an old protocol that was deprecated to make youtube work best only on their browser. A move in itself qualifying as sabotage of a competing product. It is only possible because Alphabet controls a lot of the infrastructure, people use(more on that a few paragraphs down).

Mozilla needs money so they make a deal with Google keeping it as the default search-engine, which means giving revenue to their competitors since Alphabet also produces the Chrome-Browers.

IMHO, Mozilla is not at fault here. The everything is free mentality and the economic playing field is. Alphabet, Facebook, Microsoft and Apple are the Robber Barons of the 21st century. Just like Rockefeller et all were a hundred some years ago.

We now see first hand what happens if they are not reeled in and not split up. There is an eerie similarity to what happened with the old barons. Thankfully that process gained some tracking in some countries and I do hope it will continue.

Yes I am aware there is Chromium, Iron, Brave, Opera, but I am cautious and wouldn't want to touch them with a 10 foot pole, because the rendering-engine is provided by Alphabet which thrives on information gathered against the users will. All nice products, but my argument here is the same as the one against foreign chips in domestic security products. There is always this hint of doubt. One only has to look at the development-frameworks e.g. Facebook offered for free turning every app based on them into a data gathering tool.

So I can only agree with posters below: FF is superior and more innovative and secure than Chrome and most people wanna be hip, not have to think and that is where the bigger advertisement-budget comes in.

If one screams loud enough, people apparently do believe it is healthy to eat a certain brown excrement while being part of that a huge surveillance botnet that is Google.

//Edit: Here is the source of my claim regarding Youtube https://www.zdnet.com/article/former-mozilla-exec-google-has...

//Edit2: And regarding security and innovation in that area. Google was very innovative. It dropped Certificate Pinning for their Chrome-Browser. The only thing that alerts one do MITM-Attacks if an attacker gains access to a key for signing a certificate. IMHO one more reason to stick with FF or move over. These days people think what Chrome provides is everything there is. I for myself vote with my wallet. Adblocker(because Alphabet also runs an ad-provider, also for other sides), I do not use Google as search-engine and if I must hooktube instead of youtube :)

Re:Mozilla’s Uncertain Future by 1vuio0pswjnm7 on Saturday August 15, 2020 @08:05AM (#24168281)
"That was a fundamental mistake."

I have the same opinion. Yet multiple times I have been "corrected" on HN by former/current Mozilla employees that this strategy of trying to match every new feature in Chrome was the only option. Seems like there are some fundamental disagreements between Firefox developers and Firefox users. Whenever I read the Firefox developer discussions I always feel the tone is that "we know best". Other users do not have a voice. Sure you can donate to the Foundation, but as stated in the OP Firefox developers are employed and paid by the Corporation. I sincerely doubt they are interested in any constructive feedback from other users, even if they are supporters.