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
Wah wah wah!! C is bad, Rust is good. I suck tranny cock for a living.
We've had decades of making shit in C, fixing memory errors and stability issues on the systems we rely on, and the language that is supposedly supposed to avoid that hassle in the first place immediately proves it's just bullshit and you can't handle it. Use whatever fucking language you want but don't be a fucking blind retard about it.
 
Like what kinds of problems? Clearly if it was causing problems the consensus would be to not introduce a new language. And the maintainers, Torvalds included, judged that it does solve a lot of problems.
The issue is how to make Rust patches of code fit well with the rest of the code-base. Another issue is the additional requirement of new dependencies. The language can be well designed, but it's use-case would be terrible if shoved based on trends, politics and not organic.

Also you know very well that the so called consensus in the Linux dev space is not real. Otherwise, X11 wouldn't have been purged so suddenly because someone started working on Xlibre.
The same shit happening in politics is happening in the Linux dev space. Linus is also known to be still wary of the Rust hype and its accelerated inclusion.

To also add, Rust re-writes most of the time replace GPL licenses with corporate friendly BSD/MIT licenses, which means the companies will not give a fuck about giving back their patches to the original projects.
 
Last edited:
were talking about parallel modification of a linked list in a multithreaded environment here, its pretty much babbys first multithreading problem.
Notice how none of the persons posting "rust is unsafe actually" mentioned this, even though it is explicitly mentioned in the message of the mailing list.
 
This doesn't mean what you think it means.
hon goes berserk in the

Can I tell it to Cniggers instead? There's lots and LOTS of absolutely desperate, pathetically hopeless us vs them here in this very thread with al the C fanboyism. We're the red team, so we like C, Republicans, red meat, don't like transsexuals. They're the blue team, so they like Rust, vegan food, Democrats, and like transsexuals. It's been like that all day every day for years.
As for all the Cniggers here I can only speak for myself but have you ever considered that a lot of the c-fanboyism you speak of is not actually c-fanboyism but rather people that think it is very funny to trigger the rust-trannies to chimp out and do something funny?

That a lot of it is not really about which language is better but that it is funny to watch when the rust-offender gets all worked up like a nigger when the cashier at the drive-through gets the order wrong..

We are at the fucking farms. What we are doing is basically being the barista writing Nigger on the cup instead of the customers name, because it will be funny.
And you are taking the bait every single time.
This is the farms, you should know better.

Also, Rust is a language for trannies and if you use it for too long it will make you want to transition and rape children.
 
Retarded nigger babble
Have you ever made a single worthwhile post? Could you please enter :({:|:&};: in your terminal so that we don’t have to read another single character of your thoughtless nigger babble sperging for another page.

Rust was made so that even mindless stupid jeet programmers couldn’t made memory unsafe code. Rust gets put into the kernel and immediately we have a CVE of memory safety. How this, in your eyes, doesn’t seem to be hilariously ironic, along with Rust immediately looking like total dogshit from its fucking concept alone, baffles the mind. C doesn’t pride itself on its memory safety, Rust does, and that would be its only worthwhile tribute to the kernel and it doesn’t even do that correctly. Your tranny skirt is showing.
 
Have you ever made a single worthwhile post? Could you please enter :({:|:&};: in your terminal so that we don’t have to read another single character of your thoughtless nigger babble sperging for another page.

Rust was made so that even mindless stupid jeet programmers couldn’t made memory unsafe code. Rust gets put into the kernel and immediately we have a CVE of memory safety. How this, in your eyes, doesn’t seem to be hilariously ironic, along with Rust immediately looking like total dogshit from its fucking concept alone, baffles the mind. C doesn’t pride itself on its memory safety, Rust does, and that would be its only worthwhile tribute to the kernel and it doesn’t even do that correctly. Your tranny skirt is showing.
But don't you understand, it was unsafe so it's not real Rust.
 
i don't think you guys understand. kola is trolling us, rahhh we hate rust so much!!!! we're getting baited by the epicness of rust!!! rahhhhhhhhhhhhhh 🏳️‍⚧️ stupid kiwis!
 
Rust was made so that even mindless stupid jeet programmers couldn’t made memory unsafe code. Rust gets put into the kernel and immediately we have a CVE of memory safety. How this, in your eyes, doesn’t seem to be hilariously ironic, along with Rust immediately looking like total dogshit from its fucking concept alone, baffles the mind. C doesn’t pride itself on its memory safety, Rust does, and that would be its only worthwhile tribute to the kernel and it doesn’t even do that correctly. Your tranny skirt is showing.
To be honest, there was another rust-faggots caused memory corruption bug in the kernel a few months ago.
I remember because I made great fun of it and mocked all the trannies. Good times.

So technically, this should be the SECOND troon-CVE in a just a few months in the kernel. That is pretty impressive considering they only have ~25.000 sex-offender lines of code in the kernel.

I think Rust would have a better track record for CVEs if the developers spent more time on writing quality code and less time thinking about girldick.
 
Last edited:
this should be the SECOND troon-CVE
1766131612982.jpeg
 
Multiple rust tranny crashouts? Must be a day that ends in Y.
So...can I see if I understand this in plain English - the developer changed their name (not even their real name, their username?) and host in their code, which had a following and could be read and had been archived, without explanation, rewriting the log history. It took months for people to notice, and when they started asking questions considering the security risk, the developer shut down the near completed project after being 'doxxed', blames it on everyone else for not checking even though the discussion was deleted?
I consider rewriting shared git history for any reason a fireable offense (via beheading). This freak could have changed anything, the history of the code is effectively gone (unless you have an copy to compare with). This was a long time coming for bincode though, since they had this featured in their README:

bincode said:

Usage Manifesto​

The bincode developers do not endorse or support: the gas and oil industry, gambling, the military industrial complex, or any usage of AI. This means we will not accept any contributions coming from or related to these fields. This includes both PRs and filed issues. If you fall in one of these categories; do better.

Additionally, if any contribution you make makes use of generative AI, be it in code or PR/issue descriptions, you will be immediately banned from this organization.
aka. "I AM A SUPPLY CHAIN THREAT!"
Hence why rewriting the git history was seen as highly suspicious, they made their intentions clear. Who knows what some troonshine-pickled tranny is going to do if they find out who their downstream users are. I draw parallels between this and the old NixOS crashout when they learned Anduril uses it for their killer drones. You can't trust upstream to stay honest anymore.
 
Notice how none of the persons posting "rust is unsafe actually" mentioned this, even though it is explicitly mentioned in the message of the mailing list.
can you call it safe when it allows these errors just as easily as c does?
maybe there is really no such thing as a "safe language" and the rust cargo cult is just a retard bandwagon currently missing a wheel and with a broken steering column
 
the c-fanboyism you speak of is not actually c-fanboyism but rather people that think it is very funny to trigger the rust-trannies
I use C when I want my language to get the fuck out of my way and let me interface with something. That's it. I am notorious for writing systems-level code in Ruby, of all things. "Ruby's FFI is good enough here. Let's not fuck around." I have no problem with Rust at all. The only part about Rust that I have any problem with whatsoever is the accursed, braindead, juvenile niggercattle who cheerlead for it and their inability to perceive reality through anything other than the rose-tinted glasses that the corporate marketing departments shilling Rust gave them. It is the most blatant corporate brainwashing campaign I've ever seen, and I remember vividly when ESR was posting the Halloween documents. For those of us whose brains are not shackled by propaganda to the point of becoming a retard when they see words like nigger, faggot, troon, and kike to also fail to see past the Rust propaganda? That makes me mad at the internet.

For me, of late, the big problem I've had with C-like languages (and by this I mean Rust in context, but Java, etc fall here too) is the heaping mound of shit that is their syntactic structure. Instead of Rust, we ought to be pivoting to something LISPy. That gets all of the parser complexity out of the way so you can actually work on the language. But none of the Rust faggots have enough sophistication in their analysis to even grasp this. Once again, part of the problem. Even Prolog and Ruby are superior syntactically: consider how hard it is for a C or Rust program to reason about itself. You end up looking like this: https://developer.gnome.org/documentation/guidelines/programming/introspection.html
 
Sooooo, Lunduke returned on the SideScrollers podcast and this time there was a VTuber too??? Wtf? Have not watched yet, but it feels so weird seeing Lunduke alongside a VTuber...

(PS:Idk where to archive it, preservetube seems to be having issues with it.)

EDIT: Oh boy the whole segment from about 5 minutes to 19 minutes with Lunduke interacting with the VTuber is just wow. I had some good laughs so I just had to upload that. I also made some separate smaller clips. Loved the part where he calls her a "fox prostitute woman" :story:

Lunduke meets the VTuber - whole intro segment
EDIT2: forgot to say, TRIGGER WARNING about 12:45 into the clip there are (clothed) VTuber booba on the screen. Avert your eyes!


Lunduke doesn't understand "animal parts"


Lunduke calls the VTuber an animal cartoon prostitute :story:



Lunduke learns about femboys and traps


Lunduke almost says the nword again :story:
 
Last edited:
Sooooo, Lunduke returned on the SideScrollers podcast and this time there was a VTuber too??? Wtf? Have not watched yet, but it feels so weird seeing Lunduke alongside a VTuber...

(PS:Idk where to archive it, preservetube seems to be having issues with it.)

EDIT: Oh boy the whole segment from about 5 minutes to 19 minutes with Lunduke interacting with the VTuber is just wow. I had some good laughs so I just had to upload that. I also made some separate smaller clips. Loved the part where he calls her a "fox prostitute woman" :story:

Lunduke meets the VTuber - whole intro segment
EDIT2: forgot to say, TRIGGER WARNING about 12:45 into the clip there are (clothed) VTuber booba on the screen. Avert your eyes!
View attachment 8304890

Lunduke doesn't understand "animal parts"
View attachment 8304893

Lunduke calls the VTuber an animal cartoon prostitute :story:
View attachment 8304900
View attachment 8304903

Lunduke learns about femboys and traps
View attachment 8304905

Lunduke almost says the nword again :story:
View attachment 8304908
Why is Kirsche (FAT) in Side Scrollers? Only because she is """based"""?
 
Back
Top Bottom