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
I think many people would hate Rust much much less if it didn't have the cult like behaviour surrounding it, to require all projecrs to be re-written and dismiss it's limitations.
Rust would just be another language if the people using it weren't 99.99% insane freaks who use it as a way to exert power over other people. Downstream, people think that writing something in rust is an actual feature. They also fully believe that Rust solves all the world's problems and if you'd just convert to rust you too could be as productive at rewriting software.

Once or twice a year someone comes up with a new Minecraft server... In Rust that implements about 10% of the features, makes the front page of sites like orange reddit, and then gets abandoned. People are trying to recreate sqlite... In Rust for completely unknown reasons. The custom chat implementation here got hacked by a 13 year old who just used it to upload funny attachments, but at least it was written... In Rust!

Rust does not compile unless the code will work. There is almost no margin of error. It is very soothing to autistics. There is effectively only one right way to write code in Rust.
 
Rust would just be another language if the people using it weren't 99.99% insane freaks who use it as a way to exert power over other people. Downstream, people think that writing something in rust is an actual feature. They also fully believe that Rust solves all the world's problems and if you'd just convert to rust you too could be as productive at rewriting software.
I worry that people will rely too much on Rust and won't treat Rust code with the same scrutiny as C code, perhaps thinking that Rust will catch all the memory errors. Arguably, this has already happened. People still need to be held as accountable as if they were writing C.
 
It is safe, if you don't explicitly use the one feature that makes it unsafe, lol. How is that surprising or controversial.
were talking about parallel modification of a linked list in a multithreaded environment here, its pretty much babbys first multithreading problem. be it rust or c, whoever fucked this up should be embarrassed. whats the point of introducing a hugely convoluted language like rust for safety if its programmers are still going to make elementary mistakes like this? can it ever be called "safe"?
 
Could I get an explanation as to why "I call women females" is considered "alt-right terminology"?
Because trannies are real women too even though they're not females, you alt-right chud! Or maybe I'm the alt-right chud for saying they are not females? (It's true, they are not!)
 
It is safe, if you don't explicitly use the one feature that makes it unsafe, lol. How is that surprising or controversial.
It's neither surprising nor controversial, but it is an easy jab towards the faggots that keep pushing for Rust everywhere because of muh safety and then use unsafe anyway to get anything done.
 
The troon behind the Rust 'bincode' crate rewrote the git history only to change his name. When Reddit found out, he got 'doxxed'.
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 know fuck all about Rust or code, but that sounds like a planned excuse to bail, though not necessarily because the project was unsuccessful. From the alarm people where displaying, the changes must have stood out like a sore thumb - the developer's main gripe seems to be that nobody noticed sooner. Trannies aren't as sensitive to their 'deadnames' as they pretend to be.

Could I get an explanation as to why "I call women females" is considered "alt-right terminology"?
It's considered incel language because it's (often accidently) dehumanizing. You'll probably have seen Lidl Drip complain about this a few times, when men use 'females' as opposed to women, which can imply clinical disgust. Of course you can call men 'males' all you like and we'd likely never notice.
 
It's considered incel language because it's (often accidently) dehumanizing. You'll probably have seen Lidl Drip complain about this a few times, when men use 'females' as opposed to women, which can imply clinical disgust. Of course you can call men 'males' all you like and we'd likely never notice.
It reminds me when I asked someone what the terminology for transgender male/female meant, completely out of pure interest and not trying to be a dick. I was confused if the male/female meant that they were male or female or that they were transitioning to being. I proceeded to get called an ignorant piece of shit for asking an honest question, by multiple people. Pardon me for being curious and wanting to learn more. -- This was the start of my hatred for trannies, by the by. :politisperg:

It's akin to me asking "How do I install Nvidia drivers on Arch?" and getting the reply "If you don't know how to use pacman, GTFO", yeah, real helpful guys. (Just to make this OSS themed)
 
I proceeded to get called an ignorant piece of shit for asking an honest question, by multiple people.
Your honesty was the problem, just like these people openly wondering why the history of this project was suddenly under a different name. Asking a tranny to account for themselves on virtually any subject is taboo. This is why I'm guessing, from a position of total ignorance on coding, this was a bail - they pull shit like this deliberately to avoid answering questions.

Again, somebody correct me if I'm wrong, this wasn't their actual deadname, they were reassigning credit to a new username. It's like saying bringing up the name of your sock account is harassment.
 
I think many people would hate Rust much much less if it didn't have the cult like behaviour surrounding it, to require all projecrs to be re-written and dismiss it's limitations.

For example, I don't see Haskell or Go programmers wanting to replace any other language. I wonder what caused Rust to be different. Someone should make a documentary on this phenomenon.
It's because the core Rust userbase consists of sexual deviants. There's been a lot of propaganda, going back decades, that insists that a person's public actions are somehow completely divorced from what they do "behind closed doors", but you can tell from the behavior of the cabal that controls the language's amorphous "definition" that it has a lot of BDSM freaks who want to be tranny dominatrixes. They can't crush your balls with their stiletto heels while demanding that you thank them for the privilege, but changing the language to force you to rewrite a bunch of code (while blaming you for not liking the change and for any bugs that get introduced when the code is written anew) is the next best thing.
 
1766070745194.png Thing
1766070693978.png Thing,made in Rust
 
It is safe, if you don't explicitly use the one feature that makes it unsafe, lol. How is that surprising or controversial.
It doesn't matter. You can argue until you're blue in the face that Rust only mitigates a small subset of memory problems and isn't a universal cure for all memory-related bugs. If it was marketed that way, you might even have a point. The problem is, Rust was marketed incessantly as "the memory safe language", without caveats, and was sold as something that is inherently incapable of causing memory problems; yet its first CVE in the kernel is a memory problem. You're being clowned on because you refuse to understand why this is so fucking hilarious.
 
Unlike other threads where I laugh from a distance, this stuff is uncomfortably close to home. I wish programming didn’t become the defacto millennial career option.
Issues like this are why Ill go the industrial route. A fair bit less SJW action when you work in an industrial environment, especially on the maintenance/workcell integration side.
 
It doesn't matter. You can argue until you're blue in the face that Rust only mitigates a small subset of memory problems and isn't a universal cure for all memory-related bugs. If it was marketed that way, you might even have a point. The problem is, Rust was marketed incessantly as "the memory safe language", without caveats, and was sold as something that is inherently incapable of causing memory problems; yet its first CVE in the kernel is a memory problem. You're being clowned on because you refuse to understand why this is so fucking hilarious.
It's also the perfect example of the Troon mentality that is ruining modern software. They declare it "memory safe" then immediately require unsafe carveouts in order for it to be even remotely useful.
 
Back
Top Bottom