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

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
snotang said:
I'm so sick of shitlang designers trying to offload their technical debt onto the ecosystem at large.
Click to expand...
It's not offloading technical debt, bigot. This is designing from first principles using modern methodology. Which is just a fart huffing way of saying fuck maintaining your shit, my way or the highway. See also Wayland and basically anything GNOME does.
 
WielkiWapiesz2137 said:
I wonder how comparatively many memory bugs have been introduced by switching to rust instead of just sticking to C
Click to expand...
The software that has been used for decades now compared to a new, upcoming and continually changing language?
More than there are Rusty 'software' 'developers'.
 
It's like how games companies are always hiring these consultancies to fuck everything up.
"Give my loser friends a job".
 
My theory on why the rust cargo cult exists is that it just gives people something to do.

A lot of people enjoy coding but don't get a kick out of it unless they actually make something new or interesting, which isn't realistic because those things are just so complex that one would have to dedicate their entire life to accomplish any noticeable amount of work.

But now, even a script kiddy can attempt to tackle something remotely meaningful and that is making old software "safe" by rewriting it in rust.

It has nothing to do with the language actually, just literally having a semi-realistic goal that they can work towards, otherwise all of them would just fuck off to RedoxOS.
 
skunt said:
https://lists.debian.org/debian-devel/2025/10/msg00285.html
it's that time of the day again, a core system component is being rewritten to rust because [reasons]
Click to expand...
In particular, our code to parse .deb, .ar, .tar, and the
HTTP signature verification code would strongly benefit
from memory safe languages and a stronger approach to
unit testing.
Click to expand...
So, he wants to move to Rust for... safer archive parsing? The very thing the Rust community just had a huge CVE about that also affected the Python people somehow? How safe!
 
skunt said:

it's that time of the day again, a core system component is being rewritten to rust because [reasons]
Click to expand...

"If you maintain a port without a working Rust toolchain,
please ensure it has one within the next 6 months, or
sunset the port."
Click to expand...
Panzerfrau said:
Oh my fucking god it gets funnier. He got promoted to the "senior" "engineer" and announced his retarded plans to fuck up APT literally at the same day:

View attachment 8114352
Click to expand...
Oh this is going to absolutely fuck over anyone who runs Debian on any older archetecture that isn't ARM or x86_64 just because this rust faggot can't help himself. if this gets put into the next Debian version, it's supported platforms will shrink 3 sizes smaller that day .
 
Last edited:
I was just thinking about this and just how dumb it is that Debian specifically is doing it (well its forced by Ubuntu from the looks of it).

If this was arch, it would be a good choices actually for a few reasons.

  1. Its already a faster moving rolling release. So changes like this are expected.
  2. It only officially supports amd64 processors. So it wouldn't screw over a ton of platforms by moving to it.
  3. There aren't a ton of down stream projects based on it. That are specifically built for running on legacy hardware.
But debian of all the distros. It's an insane decision that likely feels like a kick in the teeth to a lot of projects based on it, and the ports for other processors. Like I want to say puppy Linux is based on it, and antix and those IIRC are built to be able to run on ancient computers.

All that said. Would it really be that hard to just fork apt at the current version? At least for the project forks, not the Debian ports. I feel like that's going to be the thing these projects end up doing.
 
I must say I really do love how these modern programmers who are too afraid of computers to learn such basic concepts as effective and safe memory management using battle tested interfaces with decades of lineage, are making decisions about how operating systems should work. If you need a programming language to handhold you through memory management you shouldn't be anywhere near the core.
 
777- said:
My theory on why the rust cargo cult exists is that it just gives people something to do.
Click to expand...
Its literally the jewish daycare meme for trannies and their chasers. You always see the same pattern with these "people", where it isn't enough that their project sees mass adoption, it HAS to be shoved down everyone's throats until you can't breathe without noticing it. Leave it to trannies to find a way to attention whore in the most annyoing way humanly possible.

prollyanotherlurker said:
But debian of all the distros. It's an insane decision that likely feels like a kick in the teeth to a lot of projects based on it, and the ports for other processors. Like I want to say puppy Linux is based on it, and antix and those IIRC are built to be able to run on ancient computers.
Click to expand...
:optimistic: but this might lead to more people adopting Devuan/MX+ antix as a downstream if they somehow manage to steer clear of this bullshit the same way they've steered clear of hard systemd dependencies for a ton of their packaged programs. There have been upsteream migration talks by Parrot and Puppy devs in the past, maybe this'll send them over (less likely for the former since a lot of modern tooling is rust-based and sysd dependent, but a man can dream).
 
prollyanotherlurker said:
Would it really be that hard to just fork apt at the current version? At least for the project forks, not the Debian ports. I feel like that's going to be the thing these projects end up doing.
Click to expand...
I remember when apt was the killer app for Debian. It's sad they would just throw it away for some autogynephilia.
 
Yo Richard Stallman lookalike niggers in this thread, I got a question.
There exist two AI benchmarks/frameworks, WinoQueer and QueerBench (respective links below)
Now from my understanding these will tell you if an AI model or wrapper is "gay or trans friendly" but couldn't an astute person use these exact models against their author's original intentions? That is to say, if I want to make a list of "gay or trans unfriendly" AI models then I could rate them by how low they score on these?

(I found them because I was trying to find a tranny LLM so I could jokingly seriously suggest it to Null to use for his coding but sadly no such thing exists just yet)

And I guess just to make an observation about how the useless fucks compiling "frameworks" like these are self-injecting themselves into the AI sector just like they've self-inserted themselves everywhere else. They sound just as fucking useless as code of conduct morons - but comedically their hard work can just be used against them to prove an AI model hasn't been injected with retarded juice to make it polite to retards.

Bonus certified horrified rating picture: https://x.com/arianna_muti/status/1857188348638450003
1762245821698.png

Besides the politics, why are these certified geniuses printing out banners with so much technical text on them? Do they understand what the purpose of physical banners is? Or what a bulletpoint or powerpoint presentation is? Sure makes me happy to know we have veritable space cadets working on the future.

edit:
This is a horrific rabbit hole to find:
1762246221674.png1762246247798.png
 
Last edited:
Unintelligence Score said:
Is "pull request: make project depend on rust for no reason at all" the new "pull request: add gay code of conduct"?
Click to expand...
If you don't mind, could you please reframe from using the term "pull request"? I have CPTSD from trauma in my past (trigger warning: unwanted sexual advances, inappropriate sexual comments) and that phrase is really upsetting to me.

Can we maybe all agree to use "Xer would appreciate" instead? Or something similar? Thank you.


Also I don't think "main branch" is safe language either. My friends uncles stepdad's second cousins bestfriend from highschool (trigger warning self harm) hung himself from a branch of a tree so having that reminded to me really triggers my anxiety and I can barely breathe
 
neger psykolog said:
couldn't an astute person use these exact models against their author's original intentions? That is to say, if I want to make a list of "gay or trans unfriendly" AI models then I could rate them by how low they score on these?
Click to expand...
This is a funny side effect and one I've been already using while playing Magic the Gathering. MtG has a very popular card search service called Scryfall which has a quite robust query system that supports every property the card has, including custom-added tags for the card art. MtG has also been pretty woke in the past few years. This means I can search for "art:lgbtq-plus" to display cards where the art contains faggots but I can also negate this tag using the minus symbol ("-art:lgbtq-plus") to exclude all cards where the art contains faggots and achieve the effect you speak of.
 
skunt said:
could you copy/paste it?
when i check i see the same one response about someone not liking the wording and nothing else.
Click to expand...
Thread on MARC
Adrian Bunk said:
On Sun, Nov 02, 2025 at 03:13:49PM +0000, Richard Lewis wrote:
>...
> I agree with this -- i think a lot of people in debian are not used to
> communicating difficult decisions, and perhaps Debian should develop
> some policy for how to make controversial announcements (similar to the
> rule about mass bug reports)?

The announcement is just the tip of the iceberg here,
it is not even the biggest issue.

A random DD cannot just make a decision to destroy many years of work
by multiple DDs.

Communicating the decision is not a problem when the decision was made
in a civilized way.

cu
Adrian
Click to expand...
message

The thread was mostly about the tone of the announcement for a while, but has now moved on to procces/organization stuff and people calling each other "toxic" and whatnot. Some technical stuff also included, but mostly as gotchas.
Some excerpts from my favorite slapdown there:
David Kalnischkies said:
Am Fri, Oct 31, 2025 at 09:48:46PM +0100, schrieb Julian Andres Klode:
> In particular, our code to parse .deb, .ar, .tar, and the

As your goal claims to be less bugs, I would welcome to remove them all
by dropping this code from src:apt entirely. I think we can agree that
this has the least bugs & is the easiest to maintain long term.


We "need" it in two places:
- apt-ftparchive, an aging tool, which as far as I know sees its only
serious usage by your employer in the form of Launchpad, right?
Click to expand...
David Kalnischkies said:
P.S.:
Given apt is kinda the anti thesis of bundling and static linkage you
could argue that apt itself is a retro computing thing that should not
stand in the way of the modern tools and technologies that have no care
in the world for legacy concepts like shared libraries,
distribution-specific package formats and associated manager(s).

All those Debian contributors shoehorning modern software into packages
for retro computing technology like apt and dpkg…
(I am joking……… or am I?)
Click to expand...
 
Max Weber said:
Some excerpts from my favorite slapdown there:
Click to expand...
This guy is the other active APT maintainers (out of three, I think?) and he seems to hate his guts lol.

I personally love the Jean Paul guy, the one who made the initial reply. Later on someone accused him and the rest of "retrocomputing fans" of being lazy bumfucks, so he elegantly retorted pointing out a myriad of things he did to enable Rust on various architectures. And then flamed Klode again, all while staying completely polite and professional. Big admiration here, I wouldn't last two emails without calling Klode a niggerfaggot.
 
You must log in or register to reply here.
Back
Top Bottom