“ARE YOU ALL SEEING THIS”

Sjmarf@sh.itjust.works to Programmer Humor@programming.dev – 501 points –
84

You are viewing a single comment

Inb4 normies force us to change well established terminology just to appease their fragile souls

Like git's main and master

Whining about that change is kinda a red flag ngl

Right? It’s less letters and it’s pretty clear.

I haven’t found a good action neutral replacement for “black list” yet though. “Deny list” and “block list” are too action-specific.

Sounds like a nono list to me!

Or enemy list, but that might be too presidential...

Maybe you jest but now I'm seriously wondering why hasn't this been proposed. It's defo better than something like "disallow list".

I started using git after everyone switched to main from master, so I don't care about the change. But, the change in itself is a red flag.

Look, we already got rid of "Master/Slave" in favor of things like "Parent/Child", "Active/Standby", or "Primary/Secondary". We're not making more changes because right-wingers are afraid of everything.

"Okay Todd, looks like Steve is working on auth, so you'll be on the blacklist today-... ahah I mean, working on the blacklist today ahem..."

tbh i think "master" terminology is only bad if paired with "slave". the word itself kinda just lost it's original meaning
but I don't really care about git's change. im only using master out of habit

Oh yeah that was a shitshow. I made a point to keep "master" in my repos and configurations because it's the other meaning of master - one of the many others. Words are allowed to mean different things, ya know? If I'm drinking some coke I'm certainly not drugging myself (...I hope).

After all, the command to attach to a master is not "git slave", it's "git pull".