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
"patent something about your program that literally can't be coded around without compromising performance, then sue anyone who doesn't pay you"
wtf you actually have to be baiting
software patents tie with ridiculously long copyright terms, usury, herpes, usb cables that you need to rotate 3 times before they go in, and twitter for the position of "worst fucking pain in the ass man has ever had to deal with"
 
Oh, but there is... it's called: "patent something about your program that literally can't be coded around without compromising performance, then sue anyone who doesn't pay you". It's the only revenue model that demonstrably works.
This post was fact checked "TRUE" by Real Oracle Patriots. Larry Ellison nods in approval.
 
wtf you actually have to be baiting
software patents tie with ridiculously long copyright terms, usury, herpes, usb cables that you need to rotate 3 times before they go in, and twitter for the position of "worst fucking pain in the ass man has ever had to deal with"
Nope, not at all. We've now had to endure Stallman's infosocialist bullshit for over 40 years. I think we can say, with authority, that it's simply unmanageable. You can either have free software, or you can have good software, but you can't have both short of enslaving qualified programmers or otherwise duping three generations of gullible morons. Guess which was attempted (and failed).
This post was fact checked "TRUE" by Real Oracle Patriots. Larry Ellison nods in approval.
I mean, you're kinda making my point for me. He's made an ungodly amount of money, right? So I guess it works, doesn't it?

Look you two, it's not my fault that your commie pinko dreams keep getting dashed against the rocks labeled REALITY. Treating programmers as fungible entities hasn't worked, and you're living with the consequences. Maybe it's time to admit that programmers should get paid and adopt measures that ACTUALLY WORK?
 
This is actually a really fucking good idea.
Lunduke can make kino when he wants to...:cunningpepe:
Lunduke is one of the few people where I will have a polar opposite reaction between two of his videos. I can't think of anyone else, that makes one video that I completely hate, then another that brings me back around to being on his side. Usually its either all on one side, or all in the middle.
 
The thread is dead and gay, so I'm just going to double post.


Low level learning is actually saying the uutils rust rewrite makes no sense, and defeats the purpose of rewriting something in rust (like sudo makes a bit more sense).
 
(like sudo makes a bit more sense)
there is a valid reason behind rewriting stuff like sed in a memory-safety-enforcing language: there are many, many things out there that run a bunch of gnu coreutils on untrusted input
of course it probably doesn't mean much rewriting something like the gnu coreutils in rust, when said coreutils have been designed by some people that were very familiar with shitty insecure unix utilities (that often shat themselves when they got a line longer than 255 characters long or something dumb like that) and continuously maintained to be robust and efficient for the 40+ years since
 
I'm curious why the makers of rust decided to name their programming language after literal rot and decay.
Rust was named for the group of fungi that are "over-engineered for survival".
Rusts are among the most harmful pathogens to agriculture, horticulture and forestry. Rust fungi are major concerns and limiting factors for successful cultivation of agricultural and forest crops.
Oh wait, never mind. They named it after a parasitic fungal pathogen that rots plants. Very trustworthy.
 
Low level learning is actually saying the uutils rust rewrite makes no sense, and defeats the purpose of rewriting something in rust (like sudo makes a bit more sense).
The argument that coreutils doesn't span any trust boundaries is simply false. Just about any command that operates on a file can operate on a file owned by a different user, and if coreutils were to completely trust that input to, for example, be static, it would be trivial to get it to do things like copy arbitrary files, delete arbitrary files, etc.

For some reason people keep assuming that there are no true multi-user systems, ignoring that all it takes to create one is for an attacker to compromise a privilege separation user.

Also, "there is a huge movement right now, in the G-N-U community, to create a rewrite of all the coreutils in linux, in rust" - first 10 seconds. No, I don't think that GNU is pushing for its coreutils to be replaced with permissively-licensed ones, pretty sure this is just a Canonical thing.
 
I'm curious why the makers of rust decided to name their programming language after literal rot and decay.

Lay not up for yourselves treasures upon earth, where moth and rust doth corrupt, and where thieves break through and steal: (Matthew 6:19)

Your gold and silver is cankered; and the rust of them shall be a witness against you, and shall eat your flesh as it were fire. Ye have heaped treasure together for the last days. (James 5:3)

I'd reckon they picked the name because they're illiterate atheist faggots.
 
Also, "there is a huge movement right now, in the G-N-U community, to create a rewrite of all the coreutils in linux, in rust" - first 10 seconds. No, I don't think that GNU is pushing for its coreutils to be replaced with permissively-licensed ones, pretty sure this is just a Canonical thing.
nigger can't even pronounce GANOO right? shame
 
Rofl no, Rust sucks eggs and no one worth their salt on the GNU side of things is even remotely thinking about doing RIIR shit. If they were to try and rewrite it in Scheme, however....
 
What is all this retardation about Git and Rust that's making the rounds on Xitter? That Git won't work without Rust, what?
Also, if true, I'm evermore vindicated for sticking with SVN all these years. Thank God for Subversion, the truest of version controls.

Edit:
Rust is going to be a mandatory part of Git 3.0.
“On Git 3.0, nothing will work without Rust because it will be mandatory,” says Git developer Brian Carlson (who, according to his bio has pronouns of “They/Them”, and is a “cat parent”).
“Without Rust [a Git 3.0 build] will simply die and say that’s not supported.”
Up until now, Git was primarily developed in C.
G1KqS2TXkAAXH3m.webpG1KqS2YWIAAh5z-.webpG1KqS2MXgAEGy4c.webp
By The Lunduke Journal | XCancel

core utils rewritten in rust
git is now going that direction
RIIR movement is alive and well
By ThePrimeagen | XCancel
 
Last edited:
What is all this retardation about Git and Rust that's making the rounds on Xitter? That Git won't work without Rust, what?
Also, if true, I'm evermore vindicated for sticking with SVN all these years. Thank God for Subversion, the truest of version controls.
Mercurialbros...
 
Back
Top Bottom