I use FF as a primary browser on Desktop and Nightly in Android. There's much I could say about FF, but I think it would be futile.
In Debian, I'd use FF-LTS and regular FF. Since moving to Void, xbps allows only one version, so I use FF and Vivaldi.
I'd appreciate any opinions on Vivaldi. It's the only functional alternative browser I've found in the repos. But I have to start it with:
LIBGL_ALWAYS_SOFTWARE=1
Which sucks, and applies to OpenShot and a lot of other software that gets fussy with intel chips in some versions of Linux. Chromium I prefer to avoid, and it wants a password to initiate, which I understand but refuse to comply with. But that's all aside the point. Opinions, please...
> Chromium … it wants a password to initiate, which I understand but refuse to comply with.
That sounds like the the keyring issue that pops up if you have your user account auto-login on machine start. If you don't let Chromium store passwords⁰¹ this can be safely disabled: see https://archive.is/G6pPH#ID15 ²
I ran into the issue when setting up a simple temporary public kiosk a short while back.
--------
[0] I don't, I prefer to keep my internet facing UAs and my credential stores a bit more separated than that. It also removes some friction from moving between browsers, when one annoys me enough to (re)try another.
[1] If you do let Chromium store passwords, then you can still do this, but not safely as per the warnings in that article.
In Debian, I'd use FF-LTS and regular FF. Since moving to Void, xbps allows only one version, so I use FF and Vivaldi.
I'd appreciate any opinions on Vivaldi. It's the only functional alternative browser I've found in the repos. But I have to start it with:
Which sucks, and applies to OpenShot and a lot of other software that gets fussy with intel chips in some versions of Linux. Chromium I prefer to avoid, and it wants a password to initiate, which I understand but refuse to comply with. But that's all aside the point. Opinions, please...