Top and bottom

The issue is acronyms; there’s millions of products, schematics, datasheets, and manuals that refer to them as MISO and MOSI with no further explanation. Any new standard that doesn’t fit runs into the 15-competing-standards problem, and ought to be followed by an “AKA MISO” every time it’s used.

I’m the passive one in my relationship.

Anyway, the Sub is supposed to be the one that’s actually in control for this kind of thing

I think there’s a better way to put that. It’s often called a power exchange. Both people involved can rescind consent at any time, and there’s also negotiation that happens before scenes to set up expectations and limits, but I don’t know too many subs that want to be in control of a scene. My experience is they want to give up control in a way that is safe.

I thought the connotation was chattel slavery, not BDSM.

I’ll always like Primary/Secondary.

I’ve seen ‘Active / Passive’ used, that seems alright

That’s not always an accurate description though.

Consider a redundant two node database system where the second node holds a mirrored copy of the first node. Typically, one node, let’s call it node1, will accept reads and writes from clients and the other node, let’s say node2, will only accept reads from clients but will also implement all writes it receives from node2. That’s how they stay in sync.

In this scenario node2 is not “passive”. It does perform work: it serves reads to clients, and it performs writes, but only the writes received from node1. You could say that node2 slavishly follows what node1 dictates and that node1 is authorative. Master/slave more accurately describes this than active/passive.

There’s plenty of alternative terms to use without borrowing terminology from sexual roleplay.

Do I have news for you …

the Sub is supposed to be the one that’s actually in control

This is a myth, presumably meant to be reassuring to subs that are new to BDSM, at the expense of risk awareness. In principle the sub is no more “in control” than the dom is, and in practice they are often significantly less so.

Also pub/sub is already estsblished and used as common computing abbreviations

Removed by mod

unfair treatment.

We’re talking about slavery here.

sick of having to relabel

It’s not that hard…to be accommodating.

divorced from the social issues

from your point of view

the code doesn’t care

You’re right. Call it a controller and agent. I know naming is hard, but we’re smart enough to apply our lexicon.

never use the words master or slave ever again? What’s next??

Ah, the slippery slope fallacy.

We still use master over main

The default for new repositories on GitHub has been main for awhile now. You would have had to put in effort to change it to something else. You’re a stick in the mud.

The problem with these token activism is that it’s hollow in content. The intent might be good, but the action is almost pure virtue signalling.

Slavoj Zizek pointed out in multiple interviews that there’s a pervert self-reflectiveness in the self-censorship: privileged people “enjoy” being guilty of their privilege, so it’s more about themselves rather than the people they claim to represent. “Sorry, but you were naive and unaware of people being racist when they use these words, so let me stop them and now you are protected (by me) in an inclusive atmosphere.”

A related radical freedom situation as an inverse to the above is that when friends get really close, even using racist slurs is treated as a gesture of intimacy, rather than racism. In an ideal world, the context in the public discourse would be so strong that even racist words lose their racist meaning (“oh, so you are joking as well”) rather than the opposite (assuming there’s ubiquitous “hidden” racism in the use of a word, even when there’s clearly none).

Another critique is that it presents itself as a substitute of real solutions. Instead of addressing real problems, it provides a simple “everyday” solution, very much similar to the recycling movement. Of course we need to recycle, but we should be aware that it’s not a substitute of radical real actions (e.g. stopping the big oil).

Right? I get that langauge evolves and things go in and out of fashion, but this self-censoring for things completely unrelated to the original or derogatory meanings is kind of a pointless exercise to me.

master over main

That one is the most stupid one too, because master in git doesn’t even refer to a master/slave relationship. It refers to a different meaning of the word master, namely “an original from which copies can be made”, as in master recording or master key. See 5b in the Merriam-Webster dictionary. And that’s how it’s used in git: any new branches are derived from master. Main just does not have the same nuance, because it does not imply a relationship between the branches, just that it’s somehow more important than the others.

But of course, the real reason it was changed is because for companies like github it’s easier to give in to the crazies who demand this than to fight them.

I’m a dev, and I’m the opposite. At my work, we use main over master. I thought it was a little silly when we first switched, but now I’m used to it. It’s an arbitrary label anyway – could easily use trunk/branch from SVN or release/develop or any number of other labels to keep track of code.

Hell, we got a new dev on the team a month or two ago, and he tends to name things ‘feat/do-the-thing’ instead of ‘feature/make-it-go’.

It’s not as big a deal as people online make it out to be.

unfair treatment.

We’re talking about slavery here.

sick of having to relabel

It’s not that hard…to be accommodating.

divorced from the social issues

from your point of view

the code doesn’t care

You’re right. Call it a controller and agent. I know naming is hard, but we’re smart enough to apply our lexicon.

never use the words master or slave ever again? What’s next??

Ah, the slippery slope fallacy.

We still use master over main

The default for repositories on GitHub has been main. You would have had to put in effort to change it to something else. You’re a stick in the mud.

No one told you to throw away anything. If it works for you then go wild. No one else cares what you do in private or a with your “dev friends”.

I for one love shorts words to get meaning across. “main” was just sweet, the social issue thing was a good to have.

… sounds like she was fun!

I don’t have issues with the original terminology either, and wouldn’t really care if it was changed. But if it were changed to Dom/Sun then it would reinforce the meme of the stockings wearing femboy programmer. XD

I use ‘main’ on git instead of ‘master’ now (forced to change at work) and its shorter and snappier IMO.

But yeah there are more important problems out there.

while in some ways I can see your point, I would just have a hard time saying this in a work meeting here in the deep south with black colleagues present

Welcome to Orwell-ville.

PS: im most amused by those who think the USA incented slavery.

people looking for something in their sphere of knowledge to be offended about so they can feel like they are part of “a movement”

I always thought it was just people looking for something in their sphere of influence that they could do to make a difference, no matter how small.

The computing world is known for being hostile toward most out-groups, and I’ll welcome any effort to change that, no matter how small and how silly it seems. The real change needs to be in the people but perhaps being cognizant of such details will help remind us all to be more open and welcoming

Leaving aside the problematic nature of the existing terms, the result was that people actually thought a little more about the relationships the things had and started using better/more precise terminology for the relationships: primary/secondary, active/hot/cold, parent/child, etc.

Net positive all round.

Yeah this will just piss off the anti-porn/right-wing/tradcath(?) types instead of leftist/neolib/anti-racist types.

Until proven otherwise, I assume either ignorance or malicious intentions by those who want to rename these “problematic” terms. It does nothing to improve the actual issues.

That’s because the goal is not to solve the actual issue, but to feel better because they did something. Or to avoid noise generated by lunatics online.

Until a couple of years ago, we had a brand of cheese called ‘Coon’, here in Australia.

The word isn’t used as a slur over here, and the brand was simply named after the founder about 150 years back.

But it was getting increasingly on the nose as cultural influences from the US and everywhere kept seeping in, and it reached a point where it pretty much needed an excuse or at least an explanation.

So they renamed it; now it’s ‘Cheer’.

And at the time, there was all kinds of pearl-clutching about the malicious / disingenuous / officious / vapidly-offended / white-knighting / attention-seeking / etc / etc ‘woke crowd’ stomping in and making them change everything when it was perfectly good and harmless and stuff.

Six months later, nobody gave a single shit any more. Nobody died as a result or was even mildly inconvenienced, no great cultural traditions were lost, and contrary to several predictionsm newly-empowered wokeocrats have not risen from the shadows to re-gender everyone or whatever. It’s that cheese with the blue white and green label, nobody reads it anyway.

My point is that small token changes cost virtually nothing, and even if they achieve little in and of themselves, the mere fact of people being willing to make them is of benefit. Small courtesies, you know? Returning your shopping cart. Smiling at passing dogs. It models kindness and consideration, and promotes the idea that those things have value.

Which is not to suggest that we must avoid giving offense at all consts; far from it. I’m one of those stereotypicallly abrasive genX types raised on ideals of free speech, punk rock, uncomfortable truths and loudly pointing out the elephant in the room no matter how many toes get stepped on. But when there isn’t some burning issue that needs to be addressed, niceties be damned… then yeah, small courtesies. Give people that extra bit of room even if they don’t strictly needed. It’s nice to be nice.

Look back a handful of decades at all those cultural relics that your grandparents considered harmless and invisible. Asking people to drop them may have attracted ridicule and suspicion at the time, but looking back at some of them… oh dear god, really?

Hell, I remember The Black And White Minstrel Show on TV, and if you don’t remember it yourself, it’s far worse than you’re imagining.

I like the world better without things like that, even the little seemingly-trivial ones, and even if it seems like empy virtue-signalling while you’re cleaning them up.

There is stuff that was bad, white/blacklist doesn’t make much sense, when the universal “code” for allow/disallow are green and red. Allow and deny list are much better name.

Master main, is fine by me, doesnt make much sense to call it master, its only the main branch nothing else.

Shit that didnt make sense was stuff like removing community episodes from netflix, because or “blackface” without any consideration of why its there or whether it has value, just blanket ban, it was stupid af.

There is real, actual, injustice in the world that we need to address. Computer terms are not one of them.

Removed by mod

I’d like it to be changed because I don’t like saying "is the slave working? Did you check? To my black employees.

The i2c spec–which is officially controlled by NXP–explicitly made the change in 2021:

https://www.nxp.com/docs/en/user-guide/UM10204.pdf

Updated the terms “master/slave” to “controller/target” throughout to align with MIPI I3C specification and NXP’s Inclusive Language Project

Yes, this has gotten real traction.

I think very few people mind changing it, and a few people want it changed, so it’s slowly shifting across various use cases. I’ve only discussed the change from master/slave terminology with one person that affirmatively supported the change, and they didn’t know that there’s still slavery in the world today.

I don’t know what to make of that, other than to say ending human slavery ought to be a higher priority than ending references to it.

We had one guy at work like this. He was laughed out of the meeting.

The place I’m at changed all of its documentation to student/teacher instead of master/slave.

A long time ago, in a job not so far away, I worked on a computer project where we were using Apache Jackrabbit.

I quickly learned that I needed to search for Apache Jackrabbit and not just Jackrabbit – vibrators weren’t relevant to the project.

Agreed lol. this opinion also works for the god-awfully named “gimp”

Stop discriminating then, see the sexiness in the servers, the horniness in the harddrive.

I look at “master” in our repo like you would refer to a master recording or a remaster, or similarly the gold master for when you could say a video game has gone gold.

Same for databases, master / slave does not really describe the relationship anymore. It’s a primary, secondary, control node, read only or something else.

I think that’s because in computer science most master/slave nomenclature comes from hardware with a command/control structure (still notable in things like Spark where the namenode/master node controls the data nodes).

GIT just took naming conventions from other existing design patterns (although I should probably look up sources to verify that assumption).

That’s where you should use something more like top / bottom /s

I think in this sense, master is more akin to the ‘recording’ master - The best version of the recording to which others are generated, and all parts merged; no ‘slaves’ necessarily just the ‘master’.

Master can also mean proficiency. If you say you’ve mastered a trade it doesn’t mean you enslaved the trade, you simply have complete knowledge of the trade.

So in that context, the master branch is the complete branch. The branch that other branches stem from because it’s the one with code from all the teams. You could branch from another team member’s branch but if that branch hasn’t merged from master in a while, it won’t have all the knowledge (code). When you merge in master you’re getting knowledge from elsewhere from the branch that’s aware of more things than your branch is: the branch that has mastery of the code, the master branch.

Did you know that most people are not developers, and for many other use cases “master” does in fact imply control?

Edit: I guess not

We renamed everything to keep shared pipelines working with one branch.

Yeeter/Yeetee