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

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
I was reading Learn Rust with Entirely Too Many Linked Lists (direct link) and out of curiosity I got decided to look up the author but it looked like they moved their Github account (archive):
1689045512707.png


Huh. Let's take a look at their new account to see what they've been up to recently (archive):
1689045670426.png


:story: That his most popular package is called cargo-mommy, which is apparently just a "joke" package that wraps around cargo to treat the user like a little girl should probably tell you everything you need to know about the Rust community (also, lmao at him only sponsoring another tranny).

Turns out his name is Alex Beingessner, and he's spoken at some Rust conferences before. Here he is at a meetup in 2015 looking like your run of the mill nerd (youtube link):
1689046398132.png


Now lets see him after 7 years of Rust usage (youtube link):
1689046725640.png

Rust. Not even once.
 
C++ chads keep winning
View attachment 5204810

Yes, this is real: https://archive.is/kAbZr
Dear god these people are insufferable. They sound like wine snobs. I need a language that is fruity with hints of oak.

I have a simple rule for languages: can it solve the problem I need to solve. All the fruity syntax crap is lost on me and I still consider C a pretty neat idea.
 
I was reading Learn Rust with Entirely Too Many Linked Lists (direct link) and out of curiosity I got decided to look up the author but it looked like they moved their Github account (archive):
View attachment 5204559

Huh. Let's take a look at their new account to see what they've been up to recently (archive):
View attachment 5204562

:story: That his most popular package is called cargo-mommy, which is apparently just a "joke" package that wraps around cargo to treat the user like a little girl should probably tell you everything you need to know about the Rust community (also, lmao at him only sponsoring another tranny).

Turns out his name is Alex Beingessner, and he's spoken at some Rust conferences before. Here he is at a meetup in 2015 looking like your run of the mill nerd (youtube link):
View attachment 5204571

Now lets see him after 7 years of Rust usage (youtube link):

Rust. Not even once.
Going for the "frost-bitten corpse" look, I see.

I've read that tutorial, it's a good example of the copium among the Rust community. Rather than admitting that Rust is shit as something, they treat linked lists like some obscure data structure you'd have to be a madman to use. Many such cases.
 
I have a simple rule for languages: can it solve the problem I need to solve
But the language you chose isn't performant and doesn't support this specific feature. It's basically useless and I wouldn't hire you if you used it during an interview.
I have a general rule of not apologizing when I'm not sorry, and if etiquette demands it for some reason, it is going to be a "sorry you're a piece of shit" type apology. I also won't generally apologize for something I'd do again, because an apology is an implied promise you're going to try not to repeat the offending act.

And just a general rule of never apologizing to a troon for anything but just insulting them some more instead.
They've studied this and apologizing hurts you more than helps you unless it's to a close friend. People interpret apologies as a sign of weakness and people weaponize it as such.

The pullpush/pushpull people got a bit upset at one another
 
Last edited:
C++ chads keep winning
View attachment 5204810

Yes, this is real: https://archive.is/kAbZr
The CIA recently put out a big warning not to use C and C++. I'd say it's earned its chud wings.
I just hope that the standards body doesn't take it seriously (which they are)
(:_(
I saw zero Terry style reactions to the CIA announcement, just typical tranny wobbling about rust and functional programming.
 
The CIA recently put out a big warning not to use C and C++. I'd say it's earned its chud wings.
I just hope that the standards body doesn't take it seriously (which they are)
(:_(
I saw zero Terry style reactions to the CIA announcement, just typical tranny wobbling about rust and functional programming.

I think it was actually the NSA rather than CIA. Bit weird, as the NSA has a vested interest in software being as insecure as possible, so they can use their zero-days against the Russkies.
 
I think it was actually the NSA rather than CIA. Bit weird, as the NSA has a vested interest in software being as insecure as possible, so they can use their zero-days against the Russkies.
They're banking on the Russians seeing the recommendation and doing the opposite. All part of the plan.
 
The CIA recently put out a big warning not to use C and C++. I'd say it's earned its chud wings.
I just hope that the standards body doesn't take it seriously (which they are)
(:_(
I saw zero Terry style reactions to the CIA announcement, just typical tranny wobbling about rust and functional programming.
The whole point of C (and C++) is that it's almost as close to assembler as you can get. Thus it makes it very easy to blow your foot off, or your entire leg. Modern day retard programmers should probably not use them.

Personally most of my hobby stuff is Python these days. And forays into C when I need to do wacky stuff like read I2C at wire speed on a Pico and push it out over the USB port. My work stuff is whatever they happen to be paying me for that day.
 
The whole point of C (and C++) is that it's almost as close to assembler as you can get. Thus it makes it very easy to blow your foot off, or your entire leg. Modern day retard programmers should probably not use them.

Personally most of my hobby stuff is Python these days. And forays into C when I need to do wacky stuff like read I2C at wire speed on a Pico and push it out over the USB port. My work stuff is whatever they happen to be paying me for that day.
Yeah I usually stick to Kotlin or JavaScript (yeah, yeah, give me puzzle pieces, but it's a comfy language if you know how to use it right) because they're less likely to run into memory errors like you can with C/C++ if you're not really careful.
 
So I read Drew Devault's burnout posts and I wonder: what's the odds that Drew Devault will troon out soon, like within a year or so? He clearly under stress, has gone through unspecified 'relationship' problems, associates and praises known open transsexuals and probably has hated himself, or at least aspects of himself. All known risk factors for trooning out.

I am going to say 20%.
 
I think its more probable than 20%. Drew Devault's postings look like cope and attention seeking, so when these eventually stop working (because how long can you write avout yourself on a tech blog which was to be about your work) he will come up with a new name and announce that he is now brave and stunning. He may then go and "correct" all his old published postings to remove Drew Devault from the internet, but Drew Devault will be forever in our hearts.

Who's got ideas what name he chooses and how much will it sound like a prostitute name?
 
I think its more probable than 20%. Drew Devault's postings look like cope and attention seeking, so when these eventually stop working (because how long can you write avout yourself on a tech blog which was to be about your work) he will come up with a new name and announce that he is now brave and stunning. He may then go and "correct" all his old published postings to remove Drew Devault from the internet, but Drew Devault will be forever in our hearts.

Who's got ideas what name he chooses and how much will it sound like a prostitute name?

Mentioned upthread. My guesses were the old classics, Alice and Lily. Drusilla's a possibility too.

I suspect that all male tranny-enablers are at risk of trooning out themselves...
 
Yeah I usually stick to Kotlin or JavaScript (yeah, yeah, give me puzzle pieces, but it's a comfy language if you know how to use it right) because they're less likely to run into memory errors like you can with C/C++ if you're not really careful.
I like c in that it doesn't try so hard to protect you from yourself. You don't have to jump through irritating hoops get around the nanny. That, and it has what is probably the best language book ever written for any language, K&R, covers pretty much everything you need to know from hello, world on and it's not much more than a quarter inch thick.

But, if what you write does what you need it to do, who cares what you decided you should worry about when you wrote it. The language is just the tool, not the product. If you can get what you want using brainfuck, write your code in brainfuck. If you want to write everything in VBA inside an Excel spreadsheet, go ahead. People being judgemental tells you a lot more about them than it does about you.
 
Remember a few weeks ago when Red Hat Enterprise Linux was made closed source?

Well some developments have arrived.
Not only has Oracle made a response blog

But SUSE, the company behind it's own Enterpise Linux distro and supporter of the openSUSE Distro has basically decided to invest $10 million just so they can make a fork of RHEL that won't rely on RHEL's new subscription model.
 
The whole point of C (and C++) is that it's almost as close to assembler as you can get. Thus it makes it very easy to blow your foot off, or your entire leg. Modern day retard programmers should probably not use them.
C and C++ (though I think C++ is a bit too complex for its own good) are pefectly good systems programming languages.
That you can kind understand how it will be mapped to assembler and understand how the code will perform is a feature.

The only problem is that these languages are exceptionally hard to use correctly.
If you are reckless or just a shitty programmer then, sure, you will have issues and security bugs. But if you are inexperienced, careless or just not very good you can create serious bugs in any language no matter what features or tooling it provides.
 
C and C++ (though I think C++ is a bit too complex for its own good) are pefectly good systems programming languages.
That you can kind understand how it will be mapped to assembler and understand how the code will perform is a feature.

The only problem is that these languages are exceptionally hard to use correctly.
If you are reckless or just a shitty programmer then, sure, you will have issues and security bugs. But if you are inexperienced, careless or just not very good you can create serious bugs in any language no matter what features or tooling it provides.
Despite C being my favourite language, I rated you optimistic because the moment that compiler optimisations and undefined behaviour come into play, the relationship between the C abstract machine and the generated assembly can get quite convoluted. Long gone are the days when "C is a set of macros for ASM" was anything close to true, even if almost every other language is worse in that regard.
 
Back