I've been using Palemoon, built with gcc/6.40-r1, for about a month now with only two crashes that I can think of. Otherwise it has been doing everything I need in a browser and I'm very happy with it. I still keep Firefox around, but rarely fire it up anymore.
I am curious, however, what the Palemoon devs will do once support for gcc/6.4.0 is dropped, as it straight-up won't let me build Palemoon with anything newer. I guess a person could just use the pre-built binaries from the "palemoon" overlay, but I've been building it from source from the "octopus" overlay. On 04/01/2018 05:26 PM, Ian Zimmerman wrote: On 2018-04-01 16:29, Martin Vaeth wrote: An alarm sign for me was that palemoon was eventually dropped for android after being practically unmaintained (i.e. with known open security holes) for months/years. A similar alarm sign concerning linux is that they were not able to pull the fixes for the assembler code which relied on undocumented behaviour of <=gcc-5, even months after gcc-7 was out. Even if these problems are not marked as "security" issues, they can easily be some. WTH is even assembly code _doing_ in a browser?? That is insane. now that I know this is the reason why palemoon needs gcc 4, I will definitely look into it more closely. Experience shows that it is not possible to "hide": Sooner or later a website you do have to use for some reason will require such a feature. Eventually the number of these websites increases. And then you are at a dead end. Nowadays, it has already "practically" become impossible to use exclusively lynx or (e)links; in a while it will be impossible to use a browser which does not support certain new "features". You know the economist Keynes quote about "the long run". Applies quite well here.
