Waterfox VS firefox-scripts

> [Monday](https://github.com/WaterfoxCo/Waterfox/releases/tag/G5.1.9),

With 4GB of RAM I would recommend that you use the ESR version or some lightweight fork like Waterfox that I've been testing these days. Is really lighter and can use Firefox Sync. But it has his problems. I would prefer to go with ESR and deactivating smooth scrolling if I was you.

> I wish Unity didn't die

Hi from Unity on Ubuntu 23.04.

I am running the Unity flavour:

https://ubuntuunity.org/

It uses the latest Unity 7.7, released earlier this year:

https://gitlab.com/ubuntu-unity/unity-x/unityx

I run it on 3 or 4 machines, one of which has 2 screens and one of which has 3. Works great, scales well, handles modern Ubuntu just fine.

I use it with the Waterfox browser, which integrates natively with the Unity global menu bar, without any addons or config. I am currently on -- (hits alt-H, A) -- version 5.1.9.

https://www.waterfox.net/

Post issues on Gihtub for reporting bugs. https://github.com/WaterfoxCo/Waterfox/issues

I've made sure security updates have now been available ASAP for quite a while now. G5.1.9 released on Monday, for example. This is a day before Mozilla, but mostly because Mozilla spend a day or two doing QA.

I've been a fan of Waterfox for some time now

https://extensions.gnome.org/extension/1201/extend-panel-men...

Of course, GNOME broke it in a later release. This is why no amount of extensions are an answer: they break. Extensions do not work from one release of GNOME to another, and when they fail, the whole desktop often fails.

> Also, it’s not really Gnome’s fault that linux doesn’t have as great metadata from apps to be able to display the apps’ menubars (unity could do it).

False. Gtk exposes this; Unity didn't have stored metadata on lots of apps, it just displayed the existing controls' contents somewhere else. If you run brand new Gtk apps on Unity today, they get panel menus. This was not some clever hack.

Unity is still around:

https://unityd.org/

The distro is back again:

https://ubuntuunity.org/

Brand new apps, like Waterfox, integrate with it fine although they did not exist when it was written.

https://www.waterfox.net/

> With all due respect, that is bullshit reasoning. Selectively displaying useful things is the whole point of UIs.

I disagree.

1. I want to choose what is shown or not. In order to choose, I have to be able to see it. In other words, it needs to be there at first, and then I can choose whether I want to show it or not.

If I can't see it in the first place, then how am I to know it's there?

It's the users' choice what is shown or not. It is not up to the developer to say "they don't need to see this and I'm going to hide it away."

Any piece of software that does that is user hostile.

> Otherwise why would you roll up your window?

Again: it's my choice. I get to choose. It's my computer. They are my windows. I choose if they are shown or not.

That is the point of free software: Choice.

GNOME says it's free, but it takes choices away from me. I object to that.

> Why do you have menus in the first place that hide their content until clicked?

To save space for my document. You can't show everything all the time: that is why you leave it up to the user to choose what they show and when.

(Incidentally, this is also why in my opinion the Microsoft ribbon based fluent interface fails. It tries to show far too much all at once, and the result is that it wastes a huge amount of screen space, and is actually more difficult to hunt through for what I need when I need it.)

> That is no longer the corner, so it doesn’t benefit from this law at all.

False.

Fitt's law is about target size.

https://en.wikipedia.org/wiki/Fitts%27s_law#Implications_for...

It is not about corners. It is about edges too.

By the way I do have a clue about this stuff... for example here is a screenshot of a piece of software which I designed about a dozen years which makes use of Fitt's Law.

https://twitter.com/SimplicityComps/status/54085863397497241...

> The super key is the same as the windows, or the mac command key.

So, yes, but those environments don't suddenly change your entire screen.

> Also often called Meta.

That is a different key. Meta and super are not interchangeable.

https://en.wikipedia.org/wiki/Meta_key

https://en.wikipedia.org/wiki/Super_key_(keyboard_button)

> What’s the problem here exactly? Is alt+f4 written over the screen? Or ctrl+c? Especially that the same behavior is expected from the windows start menu.

The problem here, as I'm attempting to spell out, is that there were existing conventions for this stuff, and GNOME does not respect them.

> It’s a community for its users. You clearly don’t use it nor contribute to it either by work or financially, so it is not really fair to ask someone else to work for you specifically..

No. What I do is, I write about it for a living. I analyse this stuff, I draw comparisons, I point out weaknesses and strengths. That's my job.

In my professional capacity, the GNOME foundation invited me to its GUADEC conference about six or seven years back. I asked a lot of awkward and difficult questions, because that's my job, and I didn't get invited back.

> Literally every OS and distro suck at it.

False. For example, using most other interfaces, such as XFCE, I can treat a multiscreen desktop as one big space. I can have one panel at the far left, and one on the far right, of the entire multi-monitor desktop.

But GNOME doesn't let me do that.

Why not?

> Nonetheless, I feel you are reasoning from a very biased point

Because I disagree with you, you think that I'm biased?

Do you think that everyone who disagrees with you is biased?

Have you considered that perhaps I have opinions, and can draw upon years of knowledge and experience, and make reasoned arguments based on evidence, and that is not the same thing as being biased?

> I don’t think it is as fruitful a discussion.

So because I can counter your arguments with examples and reasoning, you don't think that it's fruitful discussion?

Personally, I think that the arguments where people can defend their points, and produce evidence to back them up, are the most fruitful kind.

For a long time, I've been making use of a MacOS-esque scrollbar I found online. I'm using XiaoXiaoFlood's loader script, and I've made the necessary changes to the files mentioned here to make it able to load .js and .uc.js files again. I've also modified the script a fair bit, though reverted most as it didn't work. Currently, I'm using this one, which has simply commented out the things that rely on Services. Though, even if I add it with something like const Services = globalThis.Services || ChromeUtils.import("resource://gre/modules/Services.jsm").Services; it doesn't make much of a difference. I've also tried using a userChrome.xml file, but that doesn't do much anymore. Was around 72/75 where that stopped working right?

Though for the full value I personally really also need some sort of interface that can show individual page visits in order to answer the question "What other pages did I visit at that point in time?" (sometimes I don't remember the right keywords to find a certain page again, but only some other page I visited during the same browsing session). The built-in history view is only of limited value here, because it always only shows the most-recent visit, so as soon as you visit a page again, it moves to the front of the list again and loses its original place and history context.

As usual, there used to be an add-on for that, which was subsequently broken by the move to webextensions (and even if somebody wanted to rewrite it, the webextension API doesn't cater for its full functionality). Thankfully some kind soul has maintained a version hacked to still work even on a current Firefox (https://github.com/xiaoxiaoflood/firefox-scripts/tree/master...).

This is what you're looking for.

Heads up though, it doesn't work for most tooltips. For that, I found the only way to change them is to use the above code in an agentsheet (https://github.com/xiaoxiaoflood/firefox-scripts, see the "StyloaiX" section)

Bootstrapped extensions are supported (really, xiaoxiaoflood is the only one who maintains any popular ones).

depending on your needs existing extensions may work for you, though the ContentScript based implementations have issues, if that's not enough you can use https://github.com/xiaoxiaoflood/firefox-scripts as it allows you to run the code in the browser UI, unfortunately there's no easy to use extension (and sadly FireGestures require update to work, even with loader injected into Quantum) so you may need to work with the code a bit (or more)

do what exactly? inject code? there are many slightly different approaches, the most reliable seems to be https://github.com/xiaoxiaoflood/firefox-scripts and using an approach like that forks can add extra configs to the UI making users' lives easier

Not in the foreseeable future, but maybe achievable with userChromeJS.