Diseased Open Source Software Community - it's about ethics in Code of Conducts

  • 🔧 At about Midnight EST I am going to completely fuck up the site trying to fix something.
You weren't kidding about kurayami being meticulous, look how many issues he's filed (Link/Archive). As of writing this 98 issues are open and 138 are closed. Most open source devs would kill to have a beta tester this dedicated.

This guy is better organized than any professional QA jag i've ever worked with.
 
I mean I'm not at all surprised but fuck, that is some top-shelf exceptional degeneracy. Are there any emulators written by normal people?
Then he stopped working on it for a while, then I found out he was also a non-binary furfag autist (also with a split dick)
Even if we take weirdness as a given, why is it always some combination of furry, troon, and diapers/pedo? It's never something different like "has a weird thing for goth chicks with umbrellas eating spaghetti hoops.".

For N64 emulation, there's a video plugin called "angrylion". It works great for pretty much every game I've thrown at it. You're stuck playing at the N64s native resolution, which I know is a deal breaker for some people.
 
Even if we take weirdness as a given, why is it always some combination of furry, troon, and diapers/pedo? It's never something different like "has a weird thing for goth chicks with umbrellas eating spaghetti hoops.".

It takes a very special brand of functional autism to do emulation dev work, from what I have seen. It just so happens that brand is highly susceptible to the fetishes you mention in the first sentence, apparently.
 
Even if we take weirdness as a given, why is it always some combination of furry, troon, and diapers/pedo? It's never something different like "has a weird thing for goth chicks with umbrellas eating spaghetti hoops.".

For N64 emulation, there's a video plugin called "angrylion". It works great for pretty much every game I've thrown at it. You're stuck playing at the N64s native resolution, which I know is a deal breaker for some people.

Internet culture and the influence of communities already established.
At least the English-speaking community. Japanese or European communities might be different.
 
Even if we take weirdness as a given, why is it always some combination of furry, troon, and diapers/pedo? It's never something different like "has a weird thing for goth chicks with umbrellas eating spaghetti hoops.".

For N64 emulation, there's a video plugin called "angrylion". It works great for pretty much every game I've thrown at it. You're stuck playing at the N64s native resolution, which I know is a deal breaker for some people.
I managed to get a hold of that Mario64 unofficial source port the other night. Playing buttery smooth at 4k was pretty sweet. Xbone controller felt really comfortable, I adjusted quickly. I wonder if they can do more games like that?
 
I managed to get a hold of that Mario64 unofficial source port the other night. Playing buttery smooth at 4k was pretty sweet. Xbone controller felt really comfortable, I adjusted quickly. I wonder if they can do more games like that?
It will be a very long time before they can, as the games have to be deconstructed to C and ported by hand.
 
Even if we take weirdness as a given, why is it always some combination of furry, troon, and diapers/pedo? It's never something different like "has a weird thing for goth chicks with umbrellas eating spaghetti hoops.".

As @X Prime said, I don't think you need to be autistic to write emulators, but it sure helps. So you get all the natural overlap between that and furry/trooning out.

Thankfully, emudev autists seem to fall in the line of TDS Twitter liberals. I'm not aware of any emudevs with any substantiated evidence for being into diapers/pedo/zoosadism shit. The closest was the DOSbox devs but I couldn't find anything more on it than an anonymous comment. I can tolerate using an emulator by a furry troon, but if we're talking gas chamber levels of degeneracy, I couldn't stomach that.

The MISTer project is coded by this Russian named srg320, and they don't tolerate that kind of shit over there. If they can support 5th gen systems, I may spring for one of those and leave the software emulator degeneracy behind.

It will be a very long time before they can, as the games have to be deconstructed to C and ported by hand.

Here I thought the reverse engineering of games couldn't get more autistic than the speedrunning community.

We'll probably get Ocarina of Time next, but I doubt we'll ever get Goldeneye from these types.
 
It will be a very long time before they can, as the games have to be deconstructed to C and ported by hand.
Oh, I know. I read a bunch about it when I got it. It was really just wishful thinking. Nintendo is probably going apeshit as usual because of just this. They'd never allow it.
 
Deno 1.0, the spiritual successor to node.js also written by the original node.js author, was released the other day. And of course, someone opens a CoC pr.

Deno, surprisingly (or maybe not surprisingly given how bad nodejs governance turned out), decided to opt for a simple "be professional" statement in their contributing docs and then links to rust's CoC.

pr.png


http://archive.vn/WNoVu

Typical twitter salt ensues:

salt.png



Plenty of salt in the expanded threads.
The best part is the self cannibalism going on! Performative allies begone!

cannibalism.png


 
Last edited:
Deno 1.0, the spiritual successor to node.js also written by the original node.js author
Thanks, I already hate it.

decided to opt for a simple "be professional" statement in their contributing docs and then links to rust's CoC.
WTF, I love Deno now?

Though the Rust CoC is probably one of the better-known offenders. I guess the real contributors to Deno thought that linking to it would be enough to appease the troons.

Nope! Never give em an inch, or they'll want the whole CoC.
 
Deno 1.0, the spiritual successor to node.js also written by the original node.js author, was released the other day. And of course, someone opens a CoC pr.

Deno, surprisingly (or maybe not surprisingly given how bad nodejs governance turned out), decided to opt for a simple "be professional" statement in their contributing docs and then links to rust's CoC.

View attachment 1296140

http://archive.vn/WNoVu

Typical twitter salt ensues:

View attachment 1296141



Kat's line about how there are some PoC but they aren't aware if they are a minority or not is really telling.

How racist do you have to be to judge the worth of actual contributions by who has what skin color when that has sod all to do with the content being produced? If what is being produced is legit good, I don't care if a purple person or an albino made it, so long as it does the job.
 
"I think that is a great thing to research on your own! :)"

Peak lazy progressive internet activism - you have an opportunity to enlighten someone to your point of view and discuss its merits, but instead, "it's not my job to educate you."

For those wondering why Deno was made versus iterating on Node.js, here's an article on The Register. tl;dr: The creator saw in hindsight some design errors he had made and wanted to start fresh with better practices.
 
"I think that is a great thing to research on your own! :)"

Peak lazy progressive internet activism - you have an opportunity to enlighten someone to your point of view and discuss its merits, but instead, "it's not my job to educate you."
That's always my indicator that the answer to the original question "are there any good CoC's?" is a firm "no" since the dangerhair can't be bothered.
 
Deno 1.0, the spiritual successor to node.js also written by the original node.js author, was released the other day. And of course, someone opens a CoC pr.

Deno, surprisingly (or maybe not surprisingly given how bad nodejs governance turned out), decided to opt for a simple "be professional" statement in their contributing docs and then links to rust's CoC.

View attachment 1296140

http://archive.vn/WNoVu

Typical twitter salt ensues:

View attachment 1296141


Plenty of salt in the expanded threads.
The best part is the self cannibalism going on! Performative allies begone!

View attachment 1296142

After doing some research on my own, I have come to the conclusion that there are no good CoCs, therefore none will be added, ever.
 
How racist do you have to be to judge the worth of actual contributions by who has what skin color when that has sod all to do with the content being produced?

This is doctrine. What you don't wan't "diverse" contributors? (of course, nobody actually gives a shit about this) Racist!

"I think that is a great thing to research on your own! :)"

This is algorithmic at this point. Funny enough she's actually written articles about why CoCs are holy and necessary, I'm surprised she isn't jumping in to hock them. However she is likely correct that she is in fact dealing with someone playing dumb wrt to their (correct) suspicion of CoCs. Not sure whats worse, people openly engaging these folks as if they are going to have a good faith discussion about their power CoC play, or the algorithmic "It's immoral of me to educate you, shame you aren't with the program yet". Probably the later, but whatever, shit looks weak, know your enemy.

I found the following article offer decent analysis of whats actually going on with CoCs:


tldr, CoCs serve as a political/bureaucratic instrument used by people who don't want accountability for running a project where tribal insiders get away with blaintaint violations of common decency, respect and professionalism while simultaneously distracting from the internal backchannel, non-transparent governance. Exhibit A) Node.js foundation. Minimize accountability, grant your allies freedom to misbehave, punish your enemies into silence, present distraction and misdirection at every turn, and generally exert power via mindfuck. The enumerated lists of protected characteristics in CoCs ARE important, despite it never being taken into account during enforcement.

Or if you want to cloak outright exclusion of 50% of the population from participation, you don't have to look far to find this outright stated:

(also from that thread)
facist.png



Note how this is the first point raised about the necessity of CoCs and being right of center is now directly adjacent to fascism. Or how professionalism is now adjacent to allowing pornographic content in your project. Toats normal and we should really listen to these people about anything they have to say!!

Speaking of npm the startup crash landing into MS:


A former investor and inventor of oAuth, made a twitter thread saying:

- He lost half his money of preferred shares (holy shit!)
- npm's team sucked ass
- they focused too much on diversity instead of product and failed, but diversity is still super important.

npm-sux.png


Of course his apostasy from the evangelical progs completely overpowered his softening of the "Diversity didn't help here, but its still super important don't crucify me" message, and he ended up deleting a huge twitter account due to blowback and salt.

When presented with evidence contrary to your beliefs, its best to double down, as expected by all the former npm staff who help fuck up the company. Npm of course didn't emphasize diversity enough, and thats why it failed:

not-diverse-enough.png


 
Last edited:
When presented with evidence contrary to your beliefs, its best to double down, as expected by all the former npm staff who help fuck up the company. Npm of course didn't emphasize diversity enough, and thats why it failed:

View attachment 1298843

Hiring for diversity absolutely weakens your technical team. This should be self-evident to anyone with a functioning mind. "Hiring for competence" and "hiring for diversity" are at odds with each other. If you're hiring for diversity, you're less concerned about competence than you are the diversity checklist. You're literally hiring people because they tick boxes on the checklist regardless of whether they can actually do the work well (or at all).
 
Hiring for diversity absolutely weakens your technical team. This should be self-evident to anyone with a functioning mind. "Hiring for competence" and "hiring for diversity" are at odds with each other. If you're hiring for diversity, you're less concerned about competence than you are the diversity checklist. You're literally hiring people because they tick boxes on the checklist regardless of whether they can actually do the work well (or at all).

Especially when it's not even a compromise between two things you want (or think you want), i.e. your idea of "diversity" is "fuck you you fucking white male" (which usually includes Asians too), and "competence" is itself considered a racist concept.
 
Hiring for diversity absolutely weakens your technical team. This should be self-evident to anyone with a functioning mind. "Hiring for competence" and "hiring for diversity" are at odds with each other. If you're hiring for diversity, you're less concerned about competence than you are the diversity checklist. You're literally hiring people because they tick boxes on the checklist regardless of whether they can actually do the work well (or at all).

Especially when it's not even a compromise between two things you want (or think you want), i.e. your idea of "diversity" is "fuck you you fucking white male" (which usually includes Asians too), and "competence" is itself considered a racist concept.

The literal argument goes that if we hire 'diverse' people (e.g. non-white and/or LGBT) we'll have a better mix of ideas, experience and background. Except you end up with a cast of clowns with ALL the same background, ideas, and experience with some melanin and penetrative preference variance. Its almost like if you specifically targeted the desired qualities (mix of ideas, experience and background) you might actually get it, even if it that more closely reflects the demographic makeup of the population (in the case of silicon valley, mostly white/asian men).

But then again, anyone who's worked on any technical team knows, you don't really want a wide variety of opinion if you want the team to actually be productive.
 
Even the "mix of ideas, experience and background" argument is horseshit. When you have a group of people trying to solve a technical problem, that group gains nothing from including a petrol huffing Abo, an barely literal jogger, or a troon who just keeps talking about all the things he likes to shove up his colon. It's diverse, but it's only damaging to the project. It turns out that people who have something to offer tend to have a lot in common. Those stupid mantras like "there are no bad ideas" and "all ideas are equally valid" (yes, I literally heard someone say that) are complete nonsense.
 
Back