4 ms·
How bizarre. I can't say I've ever used Pale Moon or particularly care about it, but the behavior in that thread would have had me eject and find something diff
by cthalupa 9y ago
How bizarre. I can't say I've ever used Pale Moon or particularly care about it, but the behavior in that thread would have had me eject and find something different pretty much immediately.
Starting off with such forceful language and without a hint of wanting to deal with the issue in an amicable manner is nuts. The first guy comes across as an asshole, and no one wants to deal with assholes - it's perfectly reasonable to ask to talk with the rights holder and hope they're more reasonable.
Unfortunately, it turns out the rights holder isn't any more reasonable. An immediate 'I will not be as educational next time' is a clear threat, even though he tries to backpedal away from it later.
And then we find out that the person working on the port approached the Palemoon people days ago asking about the proper way to do things, etc.
So, in the end, we have a WIP repo that does not in any way show up in the official ports tree for OpenBSD, with someone trying to do things the Right Way, getting pushed around by two people being assholes.
Now, for the technical merit: Forcing people to use special bundled libraries instead of system libraries is dumb in the vast majority of cases, especially in something that will be running untrusted code as a basic function. Like, say, a web browser. It significantly increases the amount of work required to make sure you are running a system protected against known vulnerabilities. The reasoning seems to be that whatever they're doing in the browser seems to not play nice with the upstream libs, so they've instead started doing god know's what with libs they now bundle with it. Why don't the fix the issues in their own project? No idea. If they're actually flaws with the libs, why not submit upstream patches? Not only do you have to worry about them making sure they are quickly backporting any security related fixes, you also have to worry that whatever modifications they've made might open up new security bugs, or potentially nullify fixes from upstream.
The whole MPL style branding nonsense is also bizarre and something I think is incredibly counter to the spirit of the open source software movement. It was silly with Firefox and Iceweasel, it's silly now.
Questionable technical decisions, questionable behavior, questionable commitment to the spirit of open source software.
I'll pass.
- squarefoot 9y ago"but the behavior in that thread would have had me eject and find something different pretty much immediately." Ditto. And I speak as a PaleMoon user as it's the browser of choice on all my machines. They could be right on principle, but the OP had no right to act as an ass that way. (edit: posted by mistake on top thread)
- lsaferite 9y agoSo, the question is, have you followed through on that feeling and dumped PaleMoon as a result? The only way they feel the pain of their behavior is if users leave due to that behavior.
- squarefoot 9y agoAfter reading the whole threads both on github and Pale Moon forums, I believe the best option is to migrate everything back to Firefox and dump it. Unless they either sincerely and publicly apologize for being so rude or kick that guy off the project. But I'm not holding my breath for that.
- juliangoldsmith 9y agoUnless I'm mistaken, that guy is the head of the project. I dumped Pale Moon a while ago because it was generally terrible, and have had better luck with Waterfox.
- squarefoot 9y agoNever heard of Waterfox, from the features looks interesting, thanks for mentioning it.