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

We've seen what happens to distros that get taken over by this cancer, and what happened to FreeBSD.

The only thing that matters about software is does it work. If it doesn't, fuck off. I don't give a fuck how woke you are.

ALSO how well documented and supported it is. Getting things to just work is never as simple as it's supposed to be, especially with hardware stuff. So I stick to well supported and noob distro like Ubuntu/Debian
 
ALSO how well documented and supported it is. Getting things to just work is never as simple as it's supposed to be, especially with hardware stuff. So I stick to well supported and noob distro like Ubuntu/Debian
Eventually, if you do enough tech support on your own devices, you learn the ropes enough to be able to use distros with a little less documentation. That said, there's a certain point with documentation when too little of it renders the system useless.
 
We've seen what happens to distros that get taken over by this cancer, and what happened to FreeBSD.

They tried to pull the same shit in the Ruby community ages ago too. A few years ago Coraline Ada tried to push for a coc in this issue here. After a fuck load of discussion and trash from Caraline's people, Matz did what was right and shut the discussion down. Open source projects need strong strong leadership, otherwise these people take over and essentially destroy whatever is going on.
 
Here's a gem a friend sent me: the "Anti-Fascist MIT License", a license that straight up says "If I don't like you you must gib to a group I like".
https://archive.fo/9HQti

upload_2018-7-30_15-52-25.png

The shocking part is, this isn't from some nobody online who's contributions consist of editing readme files, this is from some numale who works on projects, projects that just so happen to mostly involve only Javascript.
upload_2018-7-30_15-54-42.png

https://archive.fo/xokET

upload_2018-7-30_15-55-59.png

https://www.linkedin.com/in/thejameskyle

upload_2018-7-30_15-57-10.png

https://archive.fo/mmgpf
 
Here's a gem a friend sent me: the "Anti-Fascist MIT License", a license that straight up says "If I don't like you you must gib to a group I like".
https://archive.fo/9HQti

View attachment 507507
The shocking part is, this isn't from some nobody online who's contributions consist of editing readme files, this is from some numale who works on projects, projects that just so happen to mostly involve only Javascript.
View attachment 507508
https://archive.fo/xokET

View attachment 507509
https://www.linkedin.com/in/thejameskyle

View attachment 507510
https://archive.fo/mmgpf

How the fuck do you only last less than a year at that many organisations?
 
How the fuck do you only last less than a year at that many organisations?
In fairness, I think this is the least bizarre thing about him.

There's two explanations which don't involve him getting fired all the time:

1) Some programmers do just like being nomadic and bouncing from company to company. Often this is in search of better pay and the instant they get a better offer, move on, though this is far from the only reason.
2) He's a contractor and was only hired to work on a specific project in these cases, so when the project completed, he's gone.

I'd tend towards 2, but either is possible. It's certainly possible he's insufferable enough to get fired all the time but the above practices are common enough I think they fit better with reality.

It's also possible that he's doing one of the above things and is insufferable but isn't anywhere long enough for HR to get involved.
 
In fairness, I think this is the least bizarre thing about him.

There's two explanations which don't involve him getting fired all the time:

1) Some programmers do just like being nomadic and bouncing from company to company. Often this is in search of better pay and the instant they get a better offer, move on, though this is far from the only reason.
2) He's a contractor and was only hired to work on a specific project in these cases, so when the project completed, he's gone.

I'd tend towards 2, but either is possible. It's certainly possible he's insufferable enough to get fired all the time but the above practices are common enough I think they fit better with reality.

It's also possible that he's doing one of the above things and is insufferable but isn't anywhere long enough for HR to get involved.

Ugh, the problem with a contractor is that he'd often stay a bit longer.

I'm going with 1. I.e. someone I wouldnt hire ever.
 
I'd tend towards 2, but either is possible. It's certainly possible he's insufferable enough to get fired all the time but the above practices are common enough I think they fit better with reality.

It's blindingly obvious he's insufferable enough to get fired all the time. The only question is whether he's capable of not spilling his spaghetti long enough that the alternate explanations are more likely.
 
Here's a gem a friend sent me: the "Anti-Fascist MIT License", a license that straight up says "If I don't like you you must gib to a group I like".
https://archive.fo/9HQti
ah god my fucking eyes

To get back on topic, I'm not surprised. Free shit is a little bit of a big thing in those circles. Just wish that these people would actually show what competency they do have at making something that runs. These people aren't even pretending to be the next Volkerding.
 
Free shit is a little bit of a big thing in those circles. Just wish that these people would actually show what competency they do have at making something that runs.

Even when they do, a lot of them don't understand how people work. Linus designed Git and it's nuts to think he's that competent. Git is top dog but there were competitors back then. The guys who made Subversion have no clue. They gave a talk about the "Myth of the Genius Programmer" as a swing at Linus' talk about Git. The guys who made Subversion would have think genius is a myth.


You can watch this if you want to grind your teeth. Even neutral bloggers saw the problems. http://lambda-the-ultimate.org/node/3342 (https://archive.is/kpycC)

A major part of Linus's sales pitch is that GIT tends to hide "bad branches" and encourages experimentation, so that you don't have to know what everybody else is doing. Ben and Brian point out the importance of community and the value of documenting failure. I should emphasize that their reasons for documenting failure is not for ridiculing or disciplining programmers, but rather to help others learn from these mistakes, and hopefully help to avoid them in the future.

Nope, nobody will ever take advantage of this. Nobody will rant about the work of others or use it to push vendettas while doing nothing. :offtopic:but what happened to Apache? Their Apache Foundation projects, like Subversion, haven't gained traction and Apache is losing ground to nginx.

If anyone thought the bold part sounds like FreeBSD's CoC, congrats on making the connection. They use Subversion.https://wiki.freebsd.org/VCSWhy#DETOUR.21
 
Even when they do, a lot of them don't understand how people work. Linus designed Git and it's nuts to think he's that competent. Git is top dog but there were competitors back then. The guys who made Subversion have no clue. They gave a talk about the "Myth of the Genius Programmer" as a swing at Linus' talk about Git. The guys who made Subversion would have think genius is a myth.


You can watch this if you want to grind your teeth. Even neutral bloggers saw the problems. http://lambda-the-ultimate.org/node/3342 (https://archive.is/kpycC)



Nope, nobody will ever take advantage of this. Nobody will rant about the work of others or use it to push vendettas while doing nothing. :offtopic:but what happened to Apache? Their Apache Foundation projects, like Subversion, haven't gained traction and Apache is losing ground to nginx.

If anyone thought the bold part sounds like FreeBSD's CoC, congrats on making the connection. They use Subversion.
People who still use subversion are my bane.
 
I can't say I've had the _pleasure_ of meeting anyone who uses subversion. But then again, there aren't that many people out there who really know how to use git either (or even how it works on a basic level for that matter).
 
I can't say I've had the _pleasure_ of meeting anyone who uses subversion. But then again, there aren't that many people out there who really know how to use git either (or even how it works on a basic level for that matter).

I have used both. Git wins the crown for usefulness, simply because it's easier to go back to earlier revisions.

Subversion is a terrible POS from a usability standpoint for anyone needing to go back in time to earlier revisions and anyone who can ignore that flaw honestly boggle my mind.
 
I can't say I've had the _pleasure_ of meeting anyone who uses subversion. But then again, there aren't that many people out there who really know how to use git either (or even how it works on a basic level for that matter).
Oh, there's plenty of grandfathered in projects that still use subversion.

And there's not really much to know about using git. You can get by, 95% of the time with "git add", "git commit -a", "git push", "git clone". That's like 95% of your workflow.

And what that provides you, even if you stick your head in the sand and refuse to learn anything else, that alone will justify using git everywhere.

It's not even like git is such a revolutionary concept. It's more that the idea of a version control system that requires a centralized server is just pants-on-head retarded.
 
And there's not really much to know about using git. You can get by, 95% of the time with "git add", "git commit -a", "git push", "git clone". That's like 95% of your workflow.

And what that provides you, even if you stick your head in the sand and refuse to learn anything else, that alone will justify using git everywhere.

It's not even like git is such a revolutionary concept. It's more that the idea of a version control system that requires a centralized server is just pants-on-head exceptional.

Yeh exactly, it just does what its supposed to do "get out of the way and let people code". Its great.
 
I never figured out how git merge works so it gets in my way then :(

Otherwise it works great
 
I never figured out how git merge works so it gets in my way then :(

Otherwise it works great
Yeah, that was tricky for me too. I just use github's merges. Although I think nowadays I'm starting to get it.
 
Back