2 ms·
I use the "long-term support" version of any software whenever possible. On Debian, that's the firefox-esr package. I suppose I'm at the age where I no longer d
by gottorf 3y ago
I use the "long-term support" version of any software whenever possible. On Debian, that's the firefox-esr package. I suppose I'm at the age where I no longer desire the bleeding edge.
- I_Am_Nous 3y agoSame, especially when the bleeding edge tends toward fun stuff like "We changed the way the engine works entirely so none of your browser extensions work anymore!" RIP classic NoScript...perhaps it mostly works the same now, but when Mozilla updated Gecko (around Firefox 58 I think) they pared back what extensions were allowed to do for security reasons and NoScript had to change a lot before it could work.
- deleted 3y ago[deleted]
- stevekemp 3y agoI've run a Debian desktop system for the past decade (and more!) and for the past few years there's been a handful of packages I install from binaries/source locally. Having an up to date browser matters to me more than almost every other package. So I install the binary beneath /opt/firefox, and update it myself whenever a new release comes out. (I even created a simple "firefox-wrapper" package to point to the binary, and provide firefox to avoid any dependency issues and avoid the need to install two versions). Otherwise I think calibre, the arduino IDE, and the go toolchain, are the only binaries I've got deployed beneath /opt, as they have historically churned a lot too.