Hacker News Reader

Comment by newscracker | Hacker News Reader

> I was very surprised to see that, years after it happened, some community members still felt hurt by this choice.

Actually, it shouldn’t be surprising at all since people lost a lot of useful functionality that still do not have replacements today. Users were not stuck on XUL as a technology. They cared about functionality and power user functionality!

I’m using mainline Firefox and not some fork that still supports XUL addons, but I still miss not having good replacements for:†

* Tab Mix Plus (I haven’t seen any replacement for this; and if you haven’t used this in the XUL world, you wouldn’t know the value of it)

* Lazarus (form saver)

* Session Manager (no, other session saving extensions still feel iffy to me)

For reasons I haven’t delved into, these extensions cannot live in a WebExtensions world today. So yes, I’m one of the people hurt by the choice not of removing XUL, but not providing alternatives even several years later.

> The main drawback is, of course, that WebExtensions do not give add-on developers as much power as the promiscuous extension mechanism. I hope that all the power that add-on developers need can eventually be added to WebExtensions API but that’s something that takes engineering power, a critical resource that we’re sorely lacking.

I don’t have a lot of hope since years have passed with progress in making some more addons work with WebExtentions but not really close to being there for other addons. Though the Firefox team has said it’s currently not planning to implement Manifest V3, if and when it does (and depending on how it does), that could potentially make uBlock Origin obsolete. That would be a much larger blow to the users.

†: Please let me know if you have suggestions for great replacements for the first two extensions.

View on HN

I'll agree this is all true for power users but I think that catering to that small number of power users at the expense of having a faster, more stable, more secure browser earlier was a major mistake.

I loved Tab Mix Plus too and yes, there are some things you still can’t do in WebExtensions that you could do before. And that sucks. But I stopped using Firefox despite those options because it was so slow and unstable, especially on the Mac. By the time it got better, it was not only too late, but Chrome had extensions.

Catering to the loyalists is what killed Firefox. What’s more important to normal users is speed, not Tab Mix Plus.

Well, Firefox is far from dead, is it?

I guess the issue is a different view of what Firefox should be; I feel that many people would be satisfied if Firefox was just a small(ish) browser catering to power users. There's nothing wrong with that: power users are users too (and there are more of them than many seem to think), and I feel that many people are somewhat frustrated that all software seems designed with only my grandmother in mind. This is an issue that extends far beyond XUL by the way.

The original design goal of Firefox was to be a "90/10" browser (relative to the old Mozilla suite). e.g. 90% of the people only need 10% of the features. Catering to power users was never the goal of Firefox and they lost users to Chrome when they did. What people want is a browser that loads webpages quickly and doesn't use a lot of system resources doing so.

Well, Mozilla included email, chat, and whatnot. Regardless of what the goals were, it did cater to power users and clearly many people don't want the direction Firefox went in.

> and clearly many people don't want the direction Firefox went in.

A majority? I doubt it. I think it’s an extremely vocal minority that don’t care about the slowness of their browser (pre-e10s, pre-quantum), about things breaking (XUL extensions) or about UI features for the broad masses.

I’d bet money that FF’s 25% in Germany would be far closer to US numbers if they stayed where those vocal people want them.

I never said majority.

All I'm saying is that based on my observations people's views on what Firefox should or should not be are different, and that this explains why people are still "angry" about the extensions breaking and such. I'm not having an argument with anyone.

That may seem like bloat today, but in those days, web mail barely existed and was inferior.

If anything, using the MUA bundled with your browser was less power-userish than using a stand-alone client.

I still miss the old Opera, including the built-in email client I used. So yeah, I agree.

Honestly, Opera is one of the best pieces of software I've ever used. It had tons of features and customizability without being slow or feeling "bloated". I never quite understood why it failed to gain marketshare 10 years ago while Firefox did.

> I never quite understood why it failed to gain marketshare 10 years ago while Firefox did.

Firefox was free and Opera wasn't. Geeks don't trust proprietary garbage.

These "most people only use 10% of the features, so we can drop the rest" ideas are just soo stupid & can quickly kill otherwise good projects. And it's not just about chasing away power users, who are about the only advocates and marketing you have. Its mainly about the 10% being different for every user, effectively covering the full feature matrix!

Exactly. There's no such thing as an average user: https://www.thestar.com/news/insight/2016/01/16/when-us-air-...

If you design your thing for the average user, it won't work well for any user.

Yet that seems to be precisely who they're targeting.

The only benefit Firefox now has over Chrome is a vague political notion of not using Google-made software, something that there isn't enough call for in the real world to drive significant marketshare. Their real differentiation was sacrificed on the altar of ease of development, and now what we're left with is an also-ran, in multiple meanings of that term.

Worse, an also-ran that's doing increasingly arational things, almost as if they're wildly groping about for the mythical marketshare.

Well, perhaps not the only thing: Tree Style Tabs opens in a sidebar in Firefox (and with user CSS, can be made to auto-expand), while in Chrome it opens in a separate window.

> I feel that many people would be satisfied if Firefox was just a small(ish) browser catering to power users.

There's no way to do that in today's environment. Browser development is extremely expensive (there's only 3 companies in the world developing competitive browser engines) so you need money. For Firefox, the only way to get serious cash is to have serious marketshare.

And in reality there isn't that many "power users". I mean, even a lot of developers (like me) use barely any extensions and in any case prefer more speed than more extensibility.

Browser development is not that expensive. Developing of Web-Engines is the dark part that sucks all the money.

> For Firefox, the only way to get serious cash is to have serious marketshare.

Not true. That's only valid if your single income is marketshare-based. Mozilla for some unknown reasons hasn't made any serious attempts in the last 15+ years to get any alternative income, instead it was satisfied with being feeding on google and yahoo, while wasting money on some obvious dead projects.

> Browser development is not that expensive. Developing of Web-Engines is the dark part that sucks all the money.

Of course, but then there's enough Chromium skins, no?

Without independent browser engine you have no clout in defining and ratifying standard (as MS recently found out) which means giving Google full control.

> Mozilla for some unknown reasons hasn't made any serious attempts in the last 15+ years to get any alternative income, instead it was satisfied with being feeding on google and yahoo, while wasting money on some obvious dead projects.

They had some feeble attempts which largely failed.

Mozilla's main expertise is still browser technology based and it is probably difficult to monetize it.

> Of course, but then there's enough Chromium skins, no?

Most of them are more than skins. A browser is the interface and whole workflow, not just the way the website is displayed.

> as MS recently found out

What do you mean?

> They had some feeble attempts which largely failed.

They had no SERIOUS attempt. Well until now at least. They did some half-assed with pocket and now VPN-reselling, but never touched real business.

> Most of them are more than skins. A browser is the interface and whole workflow, not just the way the website is displayed.

The user interface is just minor part of the browser.

Mozilla's mission is to "free the web". Something like that can't be done with slightly sleeker UI on top of monopolistic rendering engine. You need to have an influence on all levels.

> as MS recently found out

I've read it this week in some interview with the FF developers that ever since MS gave up on homegrown Edge engine and adopted Chromium/Blink their voice on the standards committee is weak and lacks clout.

No wonder. It's google who keeps strict control over chromium/blink. MS can discuss, propose, even send PRs, but it's google who will decide what gets in and what doesn't.

> They had no SERIOUS attempt. Well until now at least. They did some half-assed with pocket and now VPN-reselling, but never touched real business.

Well yeah. But it just sounds a bit simplistic to say "just earn that $500 million profits somewhere so you can sponsor your side project Firefox".

> Mozilla's mission is to "free the web". Something like that can't be done with slightly sleeker UI on top of monopolistic rendering engine. You need to have an influence on all levels.

That depends on behaviour.

> I've read it this week in some interview with the FF developers that ever since MS gave up on homegrown Edge engine and adopted Chromium/Blink their voice on the standards committee is weak and lacks clout.

As if they had much to say before... But that's the point, your influence depends on what you do and who is backing you. Chrome-Edge is just too small and Microsoft is not doing much to build their influence at the moment.

> Well yeah. But it just sounds a bit simplistic to say "just earn that $500 million profits somewhere so you can sponsor your side project Firefox".

If you have a budget of some hundred million dollars and a very big and enthuastic community, then it's very easy to make money. Even having enough money at all can make you money, though this might be ruled out for Mozilla because of their legal status.

> If you have a budget of some hundred million dollars and a very big and enthuastic community, then it's very easy to make money.

Please send some of those "3 easy steps to start earning $500 million a year" to the Mozilla, they could use them.

> If you have a budget of some hundred million dollars and a very big and enthuastic community, then it's very easy to make money. Even having enough money at all can make you money, though this might be ruled out for Mozilla because of their legal status.

Do you have ideas that can help Mozilla make money? Preferably without abandoning Firefox on the way?

I'm not OP, (and people at Mozilla have probably already considered this), but why doesn't Mozilla try a far more aggressive Wikipedia-like donation campaign?

Admittedly:

1. Wikipedia has more "users" than Firefox.

2. Despite this, the donations Wikimedia receives are only about a fifth of Mozilla's budget.

However, people use their browser far more than they use any single website and hence might be more willing to donate more to Mozilla. (For example, I love Wikipedia, but I've gotten even more value from Firefox.)

Overall, this would be unlikely to cover all of Mozilla's expenses, but I'd also be surprised if donations (after such a campaign) would be less than 10% of current revenue; in any case it'd be a valuable source of diversification.

It's possible that the legal relation between the Foundation and the Corporation doesn't make this possible.

3. If wikipedia disappeared, there's no immediate, obvious, free alternative.

Encyclopedia Britannica[0] isn't free ("libre"), but it is now free (gratis). Arguably, being libre isn't quite as indispensable in the case of cultural/educational works as it is for software.

[0] https://www.britannica.com/

It's only gratis because Wikipedia exists. If Wikipedia were to disappear you'd see a paywall on EB within minutes.

Doesn't the same also partially hold for Firefox and Chrome, though?

They wouldn't start charging for Chrome, as that's not their business model, but they might move part of their development out of (open source) Chromium and into (closed source) Chrome or further curtail extensions (e.g. adblockers) etc.

No. Firefox vs Chrome is a completely different comparison than Wikipedia vs Encyclopedia Britannica.

The first two are browsers; software, the second two are stores of knowledge.

Browsers have been free for the longest time now, they are a commodity; the 'for pay' browser market died a long time ago. Possibly that was a mistake but that's where we are now and the parties that supply browers (Mozilla, Apple, Microsoft, Google to name the bulk) all try to win marketshare because they benefit from having more users. Putting up a barrier will automatically play into the hands of the opponents.

Wikipedia is a free and much larger alternative to EB, which historically was very expensive. If Wikipedia goes away there is no longer any incentive for EB to have a free tier, which is the one thing they can do to erode support for Wikipedia a little bit.

I'm not disagreeing that (in these scenarios) EB would probably become paid-for, while Chrome never would. I'm just arguing that Chrome would become even more privacy- and user-unfriendly, which is the approximate equivalent of EB putting up paywalls. (Is paying with your attention and privacy better or worse than paying directly with money?)

Apple would continue offering a relatively privacy-friendly alternative — but would require you to switch OS to use it; Microsoft might fork Chromium, but I fear that they'd only pay lip-service to privacy.

Obviously these analyses are complicated by the fact that in both cases the forces that helped create Wikipedia/Firefox wouldn't disappear. If Wikimedia died, then people would put up their Wikipedia dumps online in their own MediaWiki instances. If Mozilla died, then people would either try to keep Firefox alive or try to maintain a set of privacy patches on Chromium. How successful they'd be is another matter...

Google has done that with Android, moving more APIs and features from the open-source AOSP core to the closed-source Google Play Services library. Google can then control which Android partners get permission to ship Google Play Services for a full-featured Android experience.

As more browsers move to a Chromium base, Google might have a similar push to move more of Google's value-add out of the open-source Chromium core to the closed-source Chrome product.

https://infogalactic.com/info/Main_Page

IIRC it started as a fork of Wikipedia from a few years ago, so no idea of its currently quality, but it exists.

Thankfully, they saw this coming, so wikipedia's licensing allows you to re-host the entire site. Useful if they ever turn crooked.

Stack overflow has the same sort of setup, for the same reason. (though, that site is far more likely to die/get perverted)

Yoric:

Plenty have been voiced over the last decade. The problem is that none of the observations are ever received in earnest. Particularly starting in the Kovacs years and onwards, MoCo folks have adopted a default stance that if you're not within the figurative walls of @mozilla.com, then there's something you just don't understand as well as the anointed ones do. Meanwhile, none of the moves that the better-knowers have made have ever panned out. And in any discussion that does occur, there are all sorts of rhetorical tricks and intellectually dishonest maneuvers that are brought out to shut the conversation down. The Corporation's insistence on its own competence at this point is a lot like the "I have people skills!" scene from Office Space, only it's not a comedy and just depressing.

There's the separate matter, which is that Mozilla's problem isn't even a lack of money. Mozilla has money (and will continue to have money for at least some time). Mozilla's problem is its profligate spending and that it has chosen for itself a set of decisionmakers with Netscape-levels of ineptitude who can't be avoided.

If course correction is even possible at this point—and it's probably not—then the question is, who are the Hewitts and Blake Rosses and Ben Goodgers in 2020? Has Mozilla leadership even fostered an environment where those types can thrive? (Spoiler alert: the answer is no.)

> if Firefox was just a small(ish) browser catering to power users. There's nothing wrong with that

Except that it couldn't work in today's world, as more and more web sites would stop working in Firefox. Firefox needs significant market share to survive with an independent browser engine. Having an independent engine is key to achieving Mozilla's mission: https://www.mozilla.org/en-US/mission/

You can build a browser focused on power users if you don't need to worry about the engine. Perhaps you want to take a look at Vivaldi?

When you have a browser that is USED by programmers, the programmers will know that their own site is bad. Problems started when it stopped being a browser for programmers and power users.

They were the ones marketing it. Mozilla cut the branch on which they were sitting and is now shocked that they lose maretshare.

Strongly disagree - I think the reason Firefox market share is in a tailspin is because once they "rationalized" the codebase by getting rid of power features - there was no moat around them to keep even simple upstarts like Edge away. Programmers often make the mistake of classifying all complexity as cruft - when much of that are use cases accumulated over time that reflect your competitive advantage - one that any competitor has to overcome. The more Firefox streamlines the more they will cede ground to better funded alternatives.

Firefox’s market share started declining when Google ran huge ad campaigns for Chrome and made some of the most popular sites on the web promote Chrome and, in the case of YouTube, run better on it. Microsoft Edge didn’t affect Firefox much, and fared equally poorly against that juggernaut.

Any theory which talks about niche features without accounting for that push is unlikely to be right.

Quibi had a big ad budget too.

Marketing gives you leg up, but at the end of the day, a product's merits have to live up to it. Both IE and Safari had an even bigger advantage than marketing by being built-in to their respective platforms, and both have lost marketshare to Chrome.

I'll say pointblank I don't know what people see in Chrome, but they clearly see something in it. To me today, Safari, Firefox, and Chrome are essentially identical, which is a bad spot to be in for everyone except the market leader, because there's no incentive to switch.

UPDATE: There's a stronger case regarding Google sabotaging Firefox, but I don't think that accounts for the magnitude of the switch, here's a detail of the accusation[0]:

> A Mozilla Program Manager named Chris Peterson accused Google of making Youtube performance slower on the Firefox explorer in July 2018. Peterson alleged that Google was aware that both Firefox and Edge, Microsoft’s browser, were performing better with regard to loading the popular video sharing platform YouTube and decided to switch to a Javascript library which was incompatible with Firefox.

Google Chrome became the dominant browser around 2012, after being released in 2008. That's an astronomically fast takeover, if there were any shenanigans that accounted for it, they'd have to be quite aggressive (and therefore discussed more at that time).

[0]: https://btcmanager.com/former-mozilla-executive-accuses-goog...

Back in the day, Chrome was faster — almost as fast as Safari to launch and faster when executing heavy sites. When it took IE and Firefox longer to load, installing Chrome was something which had an immediate benefit and Google's heavy promotion of it meant that most people gave it a try.

These days, I agree that the main problem is that any modern browser is good enough that people don't feel a huge pressure to switch. I prefer Firefox's developer tools but that's not exactly a mainstream need. The most obvious angle would be something about ad blocking and privacy where Google has significant financial incentives not to follow but I' m not sure how much of an audience that could add up to and it will definitely get hostility if effective.

> I think that catering to that small number of power users at the expense of having a faster, more stable, more secure browser earlier was a major mistake.

Catering to power users is the only reason Firefox ever had market share in the first place! Normal users do not install their own browsers. Normal users do not care about their browser. They barely even know what a browser is, other than it's the thing they use to get on the Internet.

Every bit of Mozilla's original market share came from power users wanting a browser with more features and power than Internet Explorer. And once the power users fell in love with it, they evangelized it relentlessly to their friends and family. There were campaigns for power users to go install it on grandma's computer. This is the only way Firefox ever got on a normal user's computer. (This was also the only way Firefox got headway in enterprise environments, though it would have made a lot more if Mozilla had listened to power users and system admins and added the group policy and installation options they asked for.)

Chrome crushed Firefox because it was a decent, fast browser and because of the massive marketing budget. Chrome was and is pushed hard on the biggest web properties on the world - you get notifications on Google and YouTube if you use anything other than Chrome. Various other installers also installed Chrome, unless you unchecked a box. There were TV commercials. It was the default browser on Google platforms from phones to Chromebooks. That's why Chrome won.

When Firefox killed feature after feature that catered to power users, power users cared less and less about evangelization, and some of them switched to Chrome because Firefox was becoming increasingly Chrome-like, Chrome dev tools were evidently pretty good, and many people perceived Chrome to be faster. I still use Firefox, but I honestly don't see any reason to other than ideological reasons, which are becoming increasingly tenuous and not really a winning argument even for power users.

This is why Firefox usage will continue to decline. It doesn’t matter how much faster Firefox becomes. It doesn’t matter how much easier Firefox development gets. Mozilla alienated their core user base, they aren’t coming back, and normal users are never going to start installing niche browsers that aren’t pushed hard by multi billion dollar companies. Mozilla has no path forward. They’ve screwed up irrevocably and the best they can hope for is to manage the decline and cling to their remaining user base. Unfortunately, it doesn’t look like they’re going to be able to manage even that.

I.e. new users, like friends, are cooler and more exciting than old users.

My grandmother used Tax Mix Plus several years ago. I personally found it a bit laborious, but she liked organising her reading. That was such a wonderful extension.

People on HN make the mistake of assuming that the mythical 'average' user will not use such features. And convincing them otherwise is so difficult. The folks who love your product will plumb every depth of it. Not everything needs to be dumbed down to the dirt.

> What’s more important to normal users is speed

If normal users cared about speed they can go and use Chrome. The framing in many of the comments here seems to be that there is 1 ideal that all web browsers should be working towards; and it is represented by Google Chrome. That isn't really the case, there are multiple interpretations. It is very annoying that Firefox chose the path of being Chrome-but-worse. All the people who want Chrome are using it - or chromium - and they don't need Firefox trying to implement the same thing but in red.

Firefox has lost substantial features over the years - Chatzilla for example was a great little add-on. It is quite a bold strategy to write a blog post saying "we stripped out a bunch of features, but trust me you didn't want them". Even if it is true there doesn't seem to be the level of regret here that is appropriate for trashing an ecosystem that has never recovered.

uBlock Origin is important enough to Mozilla that it's featured prominently on the add-ons pages, it was the first add-on made to work on the new Firefox for Android ("make uBlock work" was its own milestone item), and Mozilla developers have actually contributed design work back to the project. Couple this with the positioning win of having uncrippled blocking compared to Chrome, and you can rest assured that Firefox won't break uBO.

Well, that is a single addons and only one of 9 currenly allowed on Android Firefox (!!). All the other addons not on the list - bad luck!

Its nice they help an addon or two, but does not help if they neglect the overall addon API & don't even let you install other addons not on their cherry picked list, even if they would work just fine!

> Well, that is a single addons and only one of 9 currenly allowed on Android Firefox (!!). All the other addons not on the list - bad luck!

What are you talking about? When I go to the store on Firefox for Android right now, it shows me a list of 11 "featured" extensions (so 9 is already wrong). To test whether that list is exhaustive, I searched for an extension not in the list (Old Reddit Redirect). I successfully installed it and confirmed that it works. So as far as I can see, both of your claims are completely wrong.

Are you sure you are running the new Fenix based Firefox (~v79) and not the old Fennec based one (v68) ?

They are rolling the update in vawes abd not all countries are yet affected. But you can still try Fenix based Firefox by installing the Beta ir Nigtly versions

I've had my current set of extensions for at least 6 months.

Mozilla has replaced the existing Android app, Fennec, with Fenix. It has not rolled out to all users and regions yet. So some users have yet to get or even see the update.

Fenix uses a whitelist-only model for extensions, and had only around 9, last I checked. Based on some github issue comments, it seems like they'd prefer to stay with a whitelist approach for the foreseeable future.

If your extensions are important to you, you'll need to disable auto-updates for Firefox in the Play store, and avoid using 'update all' and similar - that is, if your extensions aren't on the list.

A version of the old app is available through F-Droid, but it purports to de-mozilla-fy the browser, so I presume sync and other things may not work the same.

About the addon whitelist

A couple more info points - yep, they indeed have a list of addons and if the addon is not on the list, you just can't run it, full stop. Even if no one actually tried if it is broken.

I know this as a fact as someone posted a patched build with a custom list covering many more addons. I installed that and tried two addons from that list I use on desktop Firefox. One did not work (ImTranslator), but the other run just fine (Furiganaize) as on desktop. So Firefox developpers are blocking user from using perfectly working addons as they can't be bothered to add them to their fancy list of allowed addons.

About Fennec from F-Droid

I have been using it since Mozilla broke the perfectly working Firefox install on my Android tablet with the quarter baked Fenic based release and so far I have not found anything missing even if it is supposedly cleaned up from non-free parts. But I don't use Firefox sync, so I can't comment on that.

BTW, Fenix based Firefox build is being worked on for F-Droid as well (they had to cut out all the non-free stuff Mozilla puts into a normal Firefox binary, reportedly a lot more than for Fennec) so if Fenix becomes usable one day, one can get it from a source that will not stealthily replace it by something broken.

Are you kidding me? Do you honestly think it matters if it is 9 or 11 when we lost like a million? And the ability to run our own?

I hope the new one is less of a disappointment. The current one can't even do basic stuff like search through bookmarks/history, has no awareness of various things like tags in bookmarks, overall just still missing such a vast amount of functionality from desktop.

They also made lots of promises about supporting these popular addons in WebExt era in particular, you should still be able to find plenty of meta-bugs about them on Bugzilla [1].

Of course, most of them never happen, and people are disappointed.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1226546

> * Lazarus (form saver)

Not sure what this one used to provide, but I rely a lot on Form History Control [1] to save my input before the browser crashes (which it tends to do every ~10 minutes these days) and stupid websites. I have done so for years, probably even when XUL was still a thing.

I use panorama Tabgroups as well as treestyletabs, but they have trouble coping with my 600+ tabs workflow. I think I might write my own with a graphical tree representation on a pinned tab, sort of a mindmap with tabs inside, comments, notes, etc. As this is how I would like to use my browser.

[1] https://addons.mozilla.org/en-US/firefox/addon/form-history-...

Why is your browser crashing every ten minutes? I can't tell you the last time that the desktop versions of Chrome, Firefox, or Safari crashed for me. That seems like a huge productivity issue if you have to restart the browser frequently.

It looks related to Wayland (sway). This behaviour has cropped up recently. Might be a combination of:

* Having a relatively big number of tabs (~600 in multiple tab groups)

* Having a lot of extensions

* Using sway/wayland

* Combination of the following environment variables: MOZ_ENABLE_WAYLAND=1 MOZ_WEBRENDER=1 MOZ_USE_XINPUT2=1

It used to work fine, until something broke a few weeks ago, maybe in a sway/mesa/firefox update (running ArchLinux). This was way worse when autoscroll was enabled, so I disabled it as there is a bugreport for that.

I'm on holidays, so the browser is more of a productivity sink than something else, at times. Usually I don't mind much, and might restart it or leave it. Plus, 10 minutes is kind of an overstatement (it sometimes happens faster, but last three crashes took 23, 17 and 18 minutes respectively).

I'm living on the bleeding edge, so that kind of stuff happens. I's recently gotten way worse with Qt apps as well, so I would tend to blame sway. But running it as is is a good way to find patterns that might help resolve the issues once reported. I've said a few words in #sway, but didn't get an answer.

Don't worry, I could probably change my configuration in a few seconds if I needed more stability in a pinch (use another compositor, maybe another browser): I've launched a few Qt applications with -platform xcb recently.

I'm getting errors ranging from [GFX1-]: Receive IPC close with reason=AbnormalShutdown to Gdk-Message: Error reading events from display: broken pipe

Hmm. I was using a surprisingly similar setup (Arch, Sway, and Firefox) and never had those issues, but I think I was using Firefox with XWayland instead of those environment variables. I'm glad it's not a huge pain for you.

If you have time, please file a bug with some links from your about:crashes. At least for Firefox, 600 tabs really isn't that many. (At least for us many-tab people; the more common "...but why would you ever have more than half a dozen tabs open, ever?!!" people will look at me in horror.)

I don't know for sure, but those error messages look more like what happens when one process (eg the renderer) crashes and severs its connections with others. They're probably unrelated to the actual problem.

It may be that what you're running into is a side effect of forcing WebRender on blacklisted hardware? I could imagine it starting to use a new API that's buggy in your driver. </wild-handwaving>.

I use firefox under sway with MOZ_ENABLE_WAYLAND=1 MOZ_WEBRENDER=1 and 100-ish tabs and 5-10 extensions and have not experienced crashes. Not the exact same env, but somewhat similar.

> * Having a relatively big number of tabs (~600 in multiple tab groups)

I have found this extension[0] useful, for saving my machine when I leave too many tabs open. Just make sure to whitelist things you don't want unloaded. Like infinite-scroll webpages.

[0]: https://github.com/rNeomy/auto-tab-discard

If there was no good browser with the option to use uBlock Origin, I think I would give up on the web.

Were that to ever become the case, I assume a PiHole would become a much more popular gift

A PiHole does not replace uBlock and vice versa. They can block different things at different points.

Possible replacements for Tab Mix Plus: Obviously there's no drop-in replacement for everything. Even with that aside, it's hard to make recommendations because it had so many features and probably a few were especially important to you and they might differ from the ones that were important to me.

For me, the number one feature originally was to force absolutely all popups to appear in tabs, not windows. This is actually just a built-in option now (maybe it was all along?) [1]

I used to use a feature where you could hold down the right mouse button and use the scroll wheel to switch tabs - I can't remember now whether that was provided by Tab Mix Plus or FireGestures. Anyway, now it's in FireGestures' successor, Foxy Gestures [2].

But the main recommendation is Tree Style Tab [3] (plus its own extensions [4] e.g. I use TST mouse wheel, and there seems to be a tab colouring one if that's your cup of tea). The key thing is that TST draws the tabs itself so it can make any manipulations it likes to them, which it can't do with the original tab bar in new extensions (you can hide the original tab bar [5] to avoid confusing and wasteful duplication).

I realise that laying your tabs out in a totally different way is quite a big change but it's actually an amazing change by itself. It's a much more logical way to layout tabs, and you can see more tabs at once (without resorting to multiple rows - yuck!). Once you get used to it, using a linear tab bar seems ridiculous in comparison. Plus extra vertical screen space is useful and horizontal space is typically just wasted. I recommend playing with its options a bit though; I find its default behaviour (collapsing trees automatically when you switch to another one) a bit frustrating.

[1] http://kb.mozillazine.org/Browser.link.open_newwindow.restri... (set to 0)

[2] https://addons.mozilla.org/en-GB/firefox/addon/foxy-gestures...

[3] https://addons.mozilla.org/en-GB/firefox/addon/tree-style-ta...

[4] https://github.com/piroor/treestyletab/blob/master/README.md...

[5] https://github.com/piroor/treestyletab/wiki/Code-snippets-fo...

I certainly care about having proper multiprocess support, and that was an important reason for letting go of XUL. Given the choice, I'd chose what we have now.

the one thing I still miss to this day is tamper data. a replacement is ZAP but it's nowhere near as convenient (and also much bigger in scope)

You could consider downloading the source for firefox, modifying the UI and building. Swap patches with other people and you have your "promiscuous" extensions.

Take a look at browser/base/content/browser.xhtml

... and then maintain it all yourself. Depending on what your patches do you might need to be a skilled systems level polyglot programmer. And make sure not to fall behind tracking mainline because there's new zero days all the time! Related, I sure hope you're not trying to compile on a laptop with limited RAM.

I mean that's basically how the old XPCOM extensions worked for developers.

Sort of? But the amount of effort required is much higher. Source patches require having a full dev environment, it takes much longer to build the entire browser and you also have to take on responsibility for rebasing onto upstream, dealing with security releases for the browser itself _and_ every one of the patches, and running an update infrastructure.

Extensions from other people (which is 90%+ of them even for extension developers) just need to be loaded, and your own extensions only need a text editor and something that can make zip files.

Maintaining Firefox build and update environments is a multiple-employee full-time job at Mozilla, and that's before you've even started modifying anything. It's just too much to expect an end user to do this (and even extension developers are end users most of the time).

If you go in with the intention of writing an extension rather than a general case fork then it becomes a bit easier. You know from the start that you will rebase on top of upstream over and over again, and you should write code taking that into account. Minimal changes to existing code, ideally put your code in separate files and make single line changes to existing code to install hooks. Consider what code and interfaces are stable and what changes a lot.

If you just need to modify the UI, consider userChrome.css and userChrome.js files: https://www.userchrome.org

Reply on news.ycombinator.com