felipec
In software the user is important. If you are the maintainer of a major project and you hurt the user because somebody was mean to you, you shouldn't be the maintainer of a major project.
Why does that point has to be explained?
> Do you want to rant on the internet about how right you are and how stupid everyone else is, or do you want your bug fixed?
What part of "I don't even care what they do" wasn't clear? I made my objective explicit: to show *GNOME*'s shitty practices.
I made it very clear the point wasn't about me, or my patch, it's about *their practices*.
You are not even trying to understand what DHH is saying.
This is the problem with modern discourse: people don't even listen. You don't care what DHH meant, all you care about is the hedges on speech you want to impose on others.
He never said "I want fewer non-white people".
Every rational person knows what happens to a city when there's a massive influx of immigrants. So we all know what he is talking about, and it's not what you wrongly assumed.
No, he didn't. That's something you are hallucinating he said.
No, he didn't say that.
That's what you guys on the woke left always do: create a straw man and pretend he said the most appalling things you can think of.
The real DHH did not say that.
I was banned from the RubyGems project by simply saying "no satisfactory resolution from the development team".
Now woke people are walking away from RubyGems because Ruby Central wants to align with DHH. I say good riddance.
Software should be about technical merit, not ideological agendas.
All CoC's are ever used for is to silence people the moderators don't like.
The decision being disputed is not going to be affected by the shenanigans of Hector Martin, the process is going to be followed as usual.
David Airlie summarized it nicely:
> That is the process we are committed to, everyone has a voice and gets to be heard, and we move forward in the appropriate manner with each maintainer. Bypassing maintainers is the last resort, not engaging at all with maintainers isn't a productive way forward either. Your below attempt is trying to create a technical solution to a social problem.
So the technical discussion is going to continue in order to attempt consensus and the leadership (i.e. Linus Torvalds) is going to step in only if no consensus is achieved. He is waiting for the discussion to play out.
Everyone is going to be heard, including maintainers who openly admit they don't want Rust in linux.
That's an invitation to self-reflection.
We all should consider that, in every discussion.
The opposite is to think that everyone who disagrees is by definition wrong, which can never be productive.
A body of work of an atypical programmer
The point is to convince the audience, and if you think no audience would consider the notion of a flat Earth possible, you underestimate human stupidity.
Everything should be up for debate, otherwise ideas become -- as John Stuart Mill called them: dead dogma.
Simplifying the Xz Backdoor
* I did not say the variable being static was "superior", I said they were advantages.
* If you have a large array and want a linked list with pointers to the elements, then just create a `struct node` with a pointer. The linux-style intrusive linked-list allows both use cases.
Dunning-Kruger shows again that people who believe they are proficient at reading technical articles are not as proficient as they think they are.
Sometimes the obvious needs to be stated.