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

[analrapist]

how did this even compile and why didn't -Wall tell me about this what the fuck

The above is a perfectly valid program, so we shouldn't reject it IMNSHO.
__attribute((...)) is a supported alternate spelling of __attribute__((...)).

https://gcc.gnu.org/pipermail/gcc-bugs/2011-August/385017.html

 

[Creative Username]

I compile everything with -Wall -Wextra -Werror, I'd rather disable warnings inline on a case by case basis than have it build tbh

i don't like warnings being error because sometimes i will write an empty function as a big todo comment but then the compiler complains to me about the non-void function without any return statements and i don't care enough to comment it out for real or add a __makethewarningfuckoff__((thisgarbage))
it is still a crime to pass off a warning-emitting program as something good though
also what about -Wpedantic

 

[Outer Space Traveller]

"Considered as violent language is not using the word "hung" but replacing such usage with "unresponsive" or "stalled"."

"Hung" doesn't equal "hanged by the neck until dead". Is it now violent to hang up a phone call?

Everything is violence now, because words can mean anything for trannies.

 

[HalHalliday]

are you certain this is the case? it might be not be quite as bad as you expect

From what I saw, it is a problem. But, I admit, I did not look into it as much as I probably should. At least not yet, frankly, I didn't have the willpower to do so. However, I did ask Linux grey-beards, that I know, what they think. And after answering the obvious: "Why would you want to run a 20 year-old binary?" the answer was: "Probably not." At least not for 20 years. Limit dependencies and static link what you can, as you've already said. It makes sense. But it will probably break even if it's just a trivial kernel + glibc, and mine are more complex. I don't need it to be 20 years, however, people I know seem to be fixing something on Linux all the time. If I have to recompile everything every-time the distro updates, and then also deal with, e.g., gcc and their bullshit on top of that, I would rather just run it in Wine.

stuff like nix and guix actually do this quite well (you could make a compatibility layer that emulates a gnu/linux userspace from one specific point in time and use that forever)

you could also try winelib which is like reverse cygwin (i.e. a weird library that carefully adds the windows api but not the abi)
definitely try the native interfaces first however

Thanks for the tips.

 

[Cuckoman]

__attribute__
Don't worry, I'm not judging, I do this a lot myself. I hate how the error message is worded, it makes me think the interior of the attribute is what's cooked

Error message being poorly worded? Oh, shocker, I can't believe it.

My favorite error is SIGFPE: "Floating point exception (core dumped)"

You get this for example if you divide by zero. Using INTEGER division.
Floating point division by zero works "fine" it just results in a NaN value.
But INTEGER division by zero results in a "Floating Point Exception".
Lol.

 

[Creative Username]

people I know seem to be fixing something on Linux all the time

it appeals to tinkerers, so you will see a lot of people fucking around and unfucking shit repeatedly

If I have to recompile everything every-time the distro updates

it's honestly not that bad, most libraries don't break their abi every update
also recompiles aren't the horrible thing you seem to think it is, especially if you have nice things like package managers and the various tooling that unix has to make building shit really easy
and it's also very possible we will be on a new computer architecture in 20 years too, and running binaries for different architectures is not very fun

Thanks for the tips.

also see: flatpak

i really wouldn't take 20-year binaries for granted on any platform. look at the kind of shit windows needs to do in order to maintain its compatibility, and even it still fucks up sometimes

 

[Anti Snigger]

i don't like warnings being error because sometimes i will write an empty function as a big todo comment but then the compiler complains to me about the non-void function without any return statements and i don't care enough to comment it out for real or add a __makethewarningfuckoff__((thisgarbage))

Tbh for that you can usually just return 0, nullptr, etc. I do that just out of muscle memory. I think that manually auditing warnings is a lot safer, there are very few I actually take any issue with.

also what about -Wpedantic

I use compiler extensions freely, pedantic doesn't really apply to my usecases. A lot of compiler intrinsics are very valuable for optimization, and checking for whether those are available or not is a job for autotools.

 

[polakrobak99]

Error message being poorly worded? Oh, shocker, I can't believe it.

My favorite error is SIGFPE: "Floating point exception (core dumped)"

You get this for example if you divide by zero. Using INTEGER division.
Floating point division by zero works "fine" it just results in a NaN value.
But INTEGER division by zero results in a "Floating Point Exception".
Lol.

This would never happen in Rust.

 

[Heliantheae]

> Considered as violent language is not using the word "hung" but replacing such usage with "unresponsive" or "stalled".

Yet "kill" is not considered as violent language? Killing orphans, killing parents, killing children..

Anyone going along with this lunacy should be mocked relentlessly.

 

[reactionary]

Yet "kill" is not considered as violent language? Killing orphans, killing parents, killing children..

Anyone going along with this lunacy should be mocked relentlessly.

Obligatory:

 

[Fledgling Neuromancer]

Isn't like Windows 3.0 source code released publically? Could we start from scratch with that?

Windows 3.0 is based on DOS which makes its design incredibly ancient (1981). You would be better off just writing an entirely new kernel.

 

[GNU Abyss]

Native Support being offensive is a new one...

Here's the actual guide (A). It's actually worse than expected.

General Guidelines When Writing Code or Documentation

1. Avoid using terms that have social history. Terms that can have historical significance or impact in regards to race, ethnicity, national origin, gender, age, mental and physical ability, sexual orientation, socioeconomic status, religion, and educational background.
2. Avoid using idioms and jargons. These can exclude people who don’t have particular specialized knowledge, and many idioms don’t translate from country to country. Additionally, these sometimes have origins in negative stereotypes.
3. Write inclusive examples. Try to avoid using examples in documentation that is culturally-specific to a particular country, and be sure to use diverse names.

As you can imagine, "social history", when attached to so many areas of language, produces insanity.

Socially-charged language: Language that has historical or social roots, often assuming one classification as dominant over another.

• Master, slave → primary/main, secondary/replica
• Owner, master → lead, manager, expert, primary
• Black/white should only be used to reference the color of an item; do not use to signify a positive or negative characteristic.
  • Blacklist/whitelist → deny/allow list, exclusion/inclusion list, etc.
  • Black box/white box → closed/open, opaque/transparent
  • Black hat/white hat → malicious hacker/approved hacker, hostile/friendly
• Native feature/support → core feature/support, built-in feature/support
• Pow-wow → huddle, sync, meeting
• Culture fit → values fit
• Housekeeping → cleanup, maintenance, logistics

I can't pick a favorite, so I'm proposing my own. We should rename brownouts to curryouts.

Gendered language: Language that either assumes the gender of the users and developers, or that makes assumptions of a gender.

• Man hours → labor hours, work hours
• Manpower → labor, workforce
• Guys (referring to a group) → folks, people, engineers/artists, team
• Girl/Girls (referring to women age 18 and older) → woman/women
• Middleman → middle person, mediator, liaison, go-between
• Gendered pronouns (he/him/his, she/her/hers) → they, them, theirs

Nobody tell this retard that man pages exist or you're gonna be stuck doing manual manual.

Ableist language: Language that assumes a certain state of body or mind as superior to others.

• Crazy, insane → unpredictable, unexpected, hectic
• Normal → typical, usual
• Abnormal → atypical, unusual
• Sanity Check → validation check, consistency check, logic check, gut check
• Dummy → placeholder, stub, sample

My state of mind is normal and it is superior to whoever wrote this.

Ageist language: Language that makes assumptions based on age or that reinforce an age-based stereotype.

• Grandfather, grandfathering, legacy → flagship, established, rollover, carryover

Violent language: Language that practices a degree of aggression or machismo.

• Crushing it, killing it → elevating, exceeding expectations, excelling
• Hung → stalled, unresponsive

OK, what kind of fucking assumption am I making about grandfathering? Genuinely stupid. Being old is also not a stereotype.

It's now a good time to mention who initially (A) wrote this all the way back in 2021. There are very little additions compared to the latest bullshit.

These guidelines were initially written by Barathy Rangarajan and developed by the ASWF Diversity & Inclusion Working Group in 2021, but have recently been updated through a joint effort by ASWF and AOUSD.

Barathy Rangarajan is a Software Engineer on the R&D Animation/Rigging Team at DreamWorks Animation. She is a TECHWomen Core lead and Women’s Network co-lead at DreamWorks Animation and is also a member of the ASWF Diversity & Inclusion Working Group.

Jeetification will continue until morale improves.

 

[Max Weber]

• Gendered pronouns (he/him/his, she/her/hers) → they, them, theirs

Whoa! Did these fucks just decide my pronouns for me?

Nobody tell this retard that man pages exist or you're gonna be stuck doing manual manual.

Nah, we should rename it to `woman`. Oh wait, that's the cookbook CLI!

 

[Ed Special]

Windows 3.0 is based on DOS which makes its design incredibly ancient (1981). You would be better off just writing an entirely new kernel.

GNU/Linux's foundation isn't that much newer, and Apple's doing just fine on a UNIX-based kernel. The Windows NT kernel is based on the newest technological foundation of any current mainstream OS. "Old" != inherently bad.

 

[teriyakiburns]

GNU/Linux's foundation isn't that much newer, and Apple's doing just fine on a UNIX-based kernel. The Windows NT kernel is based on the newest technological foundation of any current mainstream OS. "Old" != inherently bad.

Yeah, but MS DOS is inherently bad design.

 

[Ed Special]

Yeah, but MS DOS is inherently bad design.

Is it now? Because it's still powering a fat chunk of backend infrastructure and industrial hardware just fine, while earlier versions of NT are shitting themselves in many of the same capacities.

 

[Jotch]

Cool it with throwing stones in your glass house. You want to tell me that no Linux subreddit or forum has ever banned people for opposing views?

This post is the source of your negative attention. It's needlessly argumentative and you then react with shock that people started arguing with you:

Right, I forgot that you can never have any opinions about Windows that aren't nothing but hatred and negativity on this site or the Linux gunt guard will yell me out. Sorry for daring to enter your sacred grounds.

Why are you so surprised that the people who regular the OSS thread have a more positive opinion of Linux, open source software, than Windows, closed source software?

Also I'd want to clarify that when you talk about subreddit moderators you are talking about troons.
The OSS community is plagued with these disgusting and domineering creatures that love to inject their filthy COCs into everything. It's a sore spot for the comparitively normal people in OSS.

 

[stares at error messages]

OpenUSD is a horribly confusing name. I thought is was some sort of payment processor thing meaning "open united states dollar", not some generic world that could almost mean anything. Universal scene description could literally mean instructions you have to create scenes for a play or film, something to do with criminal forensics, like a crime scene, or any number of other stuff before I think of making Blender more compatible with proprietary slop.

Inclusive Language Guide seems to be a deliberate, not novel, attempt to make it more impossible to communicate. The concept of the "black box" was popularised by the faggot Alan Turing as a though experiment for describing an abstract machine which has a unknown implementation, so why it's problematic if its part of faggot history and faggot pride is beyond me. Another issue is that "man hours" means something. You know that it is the amount of time you, a man or women, will be putting in work for. "Work Hours" could mean the hours in the day that you go to work, like an 80 hour work week, or hours that are not holiday hours, like in the context of overtime. All the new terms ASWF wants to replace people's authentic language with are more vague and unclear. They have created such a Soviet over the language you can't even communicate anymore. Any one who tries to implement this is completely lobotomised, or will be by the end of the process.

 

[mentally retarded user]

I don't know why this is being framed as a whole "Open/FOSS Community" thing, remember, there is no community, there is no authority.
OpenUSD is yet another standard for storing 3d models that Pixar and the gayming industry is setting up.
It's "open source", but it's a commercial standard, primarily made so Pixar and other studios don't rape each other with proprietary licenses for 3D file formats.
And of course the second goal is to get coders to work on this, for free, it's not just a file format, it also has a python scripting side to generate/manipulate data. (studios love this shit for "the pipeline")
That's going to require a lot of maintaining, someone needs to do this, for free. And if it's going to be yet another tool someone is going to have to learn "for the pipeline", so making it FOSS gives it more incentive.

Pixar, Adobe, Autodesk, etc. are all Californian companies so of course they have some stupid soon-to-be-raped-because-she-voted-for-it bitch (or alternatively, Black History PhD Will "Rape Victim" Stancil) on a payroll to make up Retard Gay Nigger Guidelines.
They have to pay their dues to the Gay Retard Nigger Religion of California or else Gavin Newscum stops clearing the dry bush next to their mansions and he may also bring some brown junkies near it to play with matches.

 

[Heliantheae]

All the new terms ASWF wants to replace people's authentic language with are more vague and unclear. They have created such a Soviet over the language you can't even communicate anymore. Any one who tries to implement this is completely lobotomised, or will be by the end of the process.

These kinds of assholes don't care if their ordinances result in inefficiency, destruction, confusion, obstruction, their goal is simply to exert control over other people.