Did he actually support regulating it as a utility, or did he support that bullshit "hybrid" proposal that essentially leaves us where we are now, so we'll take our fake little cookie and STFU about it.
It's not proof, but if you look at the Init System general resolution thread on the mailing list, there's a loooong subthread where the logic behind the GR is appropriate under the debian constitution.
If your definition of "credible" extends to some douchebag on an internet forum, you've got bigger problems then people saying nasty things to you on teh webz.
Yeah, that's what the real bummer of the whole thing is. PM was a godsend before, for just that reason. I'd have been through the roof if this story had been about Palemoon instead of Mozilla making a dev-focused browser.:D
It's not a question of blame (other than the author's soapboxing I mentioned earlier), just pragmatism. I'm just too old to be playing stupid "browser loyalty" games. I've got things to do, and in this case, both Fx and Palemoon get in the way of doing them: the former with its shitty, barely-usable UX garbage, and the latter by not supporting the tools I need. Since I can "kinda sorta" get around the former with "Classic Theme Restorer" and the like, and the latter I can't get around at all, Palemoon simply isn't fit to task anymore.
Yeah, I saw that SDC was fixed. Without firebug, though, it's still a no-go. Some of my other "nice to have but not dealbreaker" extensions are still "TBD" on that list, too (like Epub Reader). Honestly, screwing with the extensions just killed any real interest I had in the project. If it wasn't for the extensions, I would have switched to Opera or Chromium back before Palemoon was even a thing.
That would, even for my simple app requiring only 5 permissions, result in a 32x increase in testing effort. Far more likely scenario: I would make sure that all needed permissions are available and, if not, just refuse to start.
It's not that bad. I don't know what set of permissions you're using, or what your app even does, but a lot of things would just be rolled into testing you're already doing. Want to test if network access is denied? Do it while you're testing how your app behaves when the phone doesn't have a WIFI or 3G/4G signal (and if your app is one of those that refuses to start without a net connection, then just please ragequit)
99% of the problems apps have with permissions managers like that is just assuming data will be there instead of doing proper input checking (data from the system is still "input"). I remember back when an "android tablet" was basically a Nook Color with a modified phone rom on it, I came across some very nosy apps that shat themselves when they tried to get a phone number.
Same thing with the user agent of the browser. I always used user agent switcher so for me that was "just use UAS as needed" moment. I used firefox for a long time, so it's nothing new to me that browser I use needs to have its user agent changed to get a proper page instead of "this is an unsupported browser" placeholder. They even provided details on user agent used and user agent one needed to use to get "compatibility mode".
Yeah, so did I. It wasn't until I realized things were breaking that I finally, reluctantly, went back to Fx. The User Agent was more of a symptom than a real problem in itself, as I see it.
And reason wasn't a "moral stand" but reality that Pale Moon isn't going to implement Australis, as a result add-ons designed to work with Australis will have broken interface components. So it needs to tell add-ons to use the old UI elements, and to do so, it needs to tell add-ons that's it's not Firefox.
If that were the only change, I might have given you that one. But I think the real one that started PM bleeding off users (at least from the ragequits in the forum. Yay internet generation) is that the "firefox compatibility mode," such as it is, was turned off by default, had no option to turn it back on (and for the life of me, I couldn't find anywhere that told us the about:Config entry to do it manually), including in the FAQ about the issue, which also went on about "freedom of browser choice." Two weeks later that was finally remedied, though still not without editorializing. If it was *just* a technical issue, he seemed to be going out of his way to make it feel like it wasn't.
FWIW, that stopped being true of pale moon with the Version 25 release. The author decided that a "moral stand" about "freedom of browser choice" was more important than keeping the compatibility that had made it (at least IMO) such an awesome alternative. It broke a ton of extensions, particularly privacy extensions that made it a dealbreaker for me.
It was a bummer. I was a huge fan of Palemoon, too.
Actually, it's the opposite of what DST does. We're adding the extra hour of sun when we don't need it, and taking it away when the argument of "wanting more light in the evening" would suggest we keep it.
I'm not sure about Wagner's operas, but don't forget the end of the Ragnarok myth: Yes, the 9 worlds are frozen in a relentless year-long winter, then destroyed in a war where gods and ettins alike are almost completely wiped out, it's pretty glum stuff. But after that's all over, you've got the two people hiding in the world tree who come out, meet Baldur and Hodr (now back from the dead) and Thor's kids, and start over.
It's like finally being able to throw out that crufty old pascal code-base and re-write it in $WHATEVER_LANGUAGE_YOU_WANT_THAT_DOESNT_START_A_FLAMEWAR. Not a bad omen at all.:)
We have that. It doesn't seem worth the trouble just to tell them off, when the ballot just gets chucked in the round file anyway.
No one actually cares whether I register a ballot or not, this whole campaign is just a scare tactic to drive their party to the polls. Whoever wins, I know I'm fucked (and no, third parties aren't a valid solution to systemic failure), so yeah... no point in jumping through hoops.
I used to do that, but then my district went electronic, so I couldn't scrawl "Eat a dick" over the ballot anymore. Decided to do my civic duty by saving gas instead, after that.
Slashdot Mirror
Did he actually support regulating it as a utility, or did he support that bullshit "hybrid" proposal that essentially leaves us where we are now, so we'll take our fake little cookie and STFU about it.
These kids will grow up and not be offended by foul language, and won't teach their kids to be offended by it either.
So if... nobody is offended by it then how, exactly, does that make it a problem?
Delightfully vivisected by Thunderf00t.
Just for clarity, the bogus claims/"research" were vivisected, not the idiot making the video.
Anita Sarkeesian. 5th video, IIRC. Delightfully vivisected by Thunderf00t.
I asked a similar question a few weeks back. It seems that FreeBSD's "pkg-ng" still has a few rough edges but is coming along pretty nicely.
It's not proof, but if you look at the Init System general resolution thread on the mailing list, there's a loooong subthread where the logic behind the GR is appropriate under the debian constitution.
I"m sure I'll be doing lots of typing of papers on my phone.
Hey, you never know. November is NaNoWriMo, after all...
I'm starting to ask myself, why does Wu continue to feed the trolls months later?
Because a shitty iPhone game can only keep one relevant for so long, maybe.
If the "SJWs, feminazis and progressives" want to make their own games they can. The market will decide what it wants.
They did. It did. That's what started this whole fucking circus.
Threaten me in a credible way and I will respond
If your definition of "credible" extends to some douchebag on an internet forum, you've got bigger problems then people saying nasty things to you on teh webz.
Yeah, that's what the real bummer of the whole thing is. PM was a godsend before, for just that reason. I'd have been through the roof if this story had been about Palemoon instead of Mozilla making a dev-focused browser. :D
It's not a question of blame (other than the author's soapboxing I mentioned earlier), just pragmatism. I'm just too old to be playing stupid "browser loyalty" games. I've got things to do, and in this case, both Fx and Palemoon get in the way of doing them: the former with its shitty, barely-usable UX garbage, and the latter by not supporting the tools I need. Since I can "kinda sorta" get around the former with "Classic Theme Restorer" and the like, and the latter I can't get around at all, Palemoon simply isn't fit to task anymore.
Yeah, I saw that SDC was fixed. Without firebug, though, it's still a no-go. Some of my other "nice to have but not dealbreaker" extensions are still "TBD" on that list, too (like Epub Reader). Honestly, screwing with the extensions just killed any real interest I had in the project. If it wasn't for the extensions, I would have switched to Opera or Chromium back before Palemoon was even a thing.
That would, even for my simple app requiring only 5 permissions, result in a 32x increase in testing effort. Far more likely scenario: I would make sure that all needed permissions are available and, if not, just refuse to start.
It's not that bad. I don't know what set of permissions you're using, or what your app even does, but a lot of things would just be rolled into testing you're already doing. Want to test if network access is denied? Do it while you're testing how your app behaves when the phone doesn't have a WIFI or 3G/4G signal (and if your app is one of those that refuses to start without a net connection, then just please ragequit)
99% of the problems apps have with permissions managers like that is just assuming data will be there instead of doing proper input checking (data from the system is still "input"). I remember back when an "android tablet" was basically a Nook Color with a modified phone rom on it, I came across some very nosy apps that shat themselves when they tried to get a phone number.
Never trust the client.
The ones that really went ape for me were "Self-Destructing Cookies" and Firebug: the former was rage-inducing, but the latter was a dealbreaker.
Same thing with the user agent of the browser. I always used user agent switcher so for me that was "just use UAS as needed" moment. I used firefox for a long time, so it's nothing new to me that browser I use needs to have its user agent changed to get a proper page instead of "this is an unsupported browser" placeholder. They even provided details on user agent used and user agent one needed to use to get "compatibility mode".
Yeah, so did I. It wasn't until I realized things were breaking that I finally, reluctantly, went back to Fx. The User Agent was more of a symptom than a real problem in itself, as I see it.
And reason wasn't a "moral stand" but reality that Pale Moon isn't going to implement Australis, as a result add-ons designed to work with Australis will have broken interface components.
So it needs to tell add-ons to use the old UI elements, and to do so, it needs to tell add-ons that's it's not Firefox.
If that were the only change, I might have given you that one. But I think the real one that started PM bleeding off users (at least from the ragequits in the forum. Yay internet generation) is that the "firefox compatibility mode," such as it is, was turned off by default, had no option to turn it back on (and for the life of me, I couldn't find anywhere that told us the about:Config entry to do it manually), including in the FAQ about the issue, which also went on about "freedom of browser choice." Two weeks later that was finally remedied, though still not without editorializing. If it was *just* a technical issue, he seemed to be going out of his way to make it feel like it wasn't.
FWIW, that stopped being true of pale moon with the Version 25 release. The author decided that a "moral stand" about "freedom of browser choice" was more important than keeping the compatibility that had made it (at least IMO) such an awesome alternative. It broke a ton of extensions, particularly privacy extensions that made it a dealbreaker for me.
It was a bummer. I was a huge fan of Palemoon, too.
That's what a memory leak is: not properly releasing memory when it's no longer needed.
Are you being snarky?
Americans, frequently.
Actually, it's the opposite of what DST does. We're adding the extra hour of sun when we don't need it, and taking it away when the argument of "wanting more light in the evening" would suggest we keep it.
You will in the spring!
I'm not sure about Wagner's operas, but don't forget the end of the Ragnarok myth: Yes, the 9 worlds are frozen in a relentless year-long winter, then destroyed in a war where gods and ettins alike are almost completely wiped out, it's pretty glum stuff. But after that's all over, you've got the two people hiding in the world tree who come out, meet Baldur and Hodr (now back from the dead) and Thor's kids, and start over.
It's like finally being able to throw out that crufty old pascal code-base and re-write it in $WHATEVER_LANGUAGE_YOU_WANT_THAT_DOESNT_START_A_FLAMEWAR. Not a bad omen at all. :)
We have that. It doesn't seem worth the trouble just to tell them off, when the ballot just gets chucked in the round file anyway.
No one actually cares whether I register a ballot or not, this whole campaign is just a scare tactic to drive their party to the polls. Whoever wins, I know I'm fucked (and no, third parties aren't a valid solution to systemic failure), so yeah... no point in jumping through hoops.
I used to do that, but then my district went electronic, so I couldn't scrawl "Eat a dick" over the ballot anymore. Decided to do my civic duty by saving gas instead, after that.