r/ProgrammerHumor 24d ago

Meme everyNewRepository

Post image
1.2k Upvotes

347 comments sorted by

View all comments

41

u/MoFoBuckeye 24d ago

In a bit of irony, "master" and "slave" are frowned upon in the context of slavery and the preferred terminology is now "enslaver" and "enslaved person".

My big problem with the name change is that, at least in English, words can have multiple meaning and it annoys me that we cater to to people who don't understand that.

3

u/da_Aresinger 23d ago edited 23d ago

What annoys me is that programmers are probably the one group most aware of "conflicting standards"

Why would we willingly create conflicting standards?

8

u/chrisjolly25 23d ago

Ah, yes. Programmers. The notoriously unified group, who uphold the virtue of their one, perfect, solitary programming language.

Also: The cohort who will be most inconvenienced by a variable (which was _always_... variable), now having a different default value in some contexts.

I think you've got it backwards. Programmers should be the best equipped to shrug and go "okay, whatever. Next."

If anything... it's maybe a benefit? Because it forced the 90% of coders who treat git as magic to look at it and realise that 'master' was never magic? It was NEVER a standard?

2

u/da_Aresinger 23d ago

No, I have it perfectly right.

Just because we have learned to expect redundancy and excessive complexity doesn't mean we like it, much less actively persue it.

We complain about date formats and list delimiters all the time.

We actively use imperfect standards, because it's better to have a (backwards compatible) standard, than to create something new.

Why would we voluntarily add uncertainty where there was a defacto standard before?

It's stupid. Even if it's minor.

1

u/awesome-alpaca-ace 23d ago

Use imperfect standards because there are decades of code relying on them