Millenials - Load"$“,8 LIST LOAD"LEISURESUIT*”,8,1 (wait 10 min.) RUN

Even the oldest millennials were just toddlers when the C64 was relevant, so this is not a typical millennial experience at all. It’s really a GenX thing… so once again we are forgotten.

I would say millennials’ computer experience starts in the late DOS/Win3.11 era at the very earliest, but more typically in the Windows 9x and early XP era. So even IRQ/DMA/config.sys/autoexec.bat fuckery is not that typical.

Take a breath dude

Can you not please with the condescending language? Maybe you’re the one who should take a breath and read my post calmly. Anyway, the guy above me asked, I gave an answer to cover all the bases.

The default branch name of git isn’t that important to me either, I’ll manage with main or master. But at the same time it does irk me especially since this kind of language policing has become an industry wide trend, and it’s just a stupid thing done for stupid reasons. Am I still allowed to express why I find it stupid?

it’s trivial to change

It isn’t as trivial as you make it out. I’ve already encountered repos where there was both a main and a master branch, both with different commits, because some developer got confused, and it was a nice mess to untangle. But hey, let’s change some more stuff around for no good reason.

If there’s any chance it helps maintain a hostile workplace/industry

I can think of a lot of things that contribute to a hostile workplace, but the default branch name of git? Seriously? Even the people who pushed for this don’t actually believe that themselves.

Why care about Master at all?

I’ve already explained all my reasons, but I’ll reiterate. To summarize I basically have five main issues with it

1. The change was done in response to attempts at language policing and bullying by a vocal and militant minority. Giving into it is a form of appeasement towards an unreasonable demand.

2. The change retroactively modifies a terminology that was already agreed upon. Like, if git sprung into existence today, not many people would have an issue with it if they would call it main or trunk or primary from the get go. But that’s not what happened. Git was released in 2005 and it used master terminology. As a consequence, many existing repositories also use master. Now when someone is working with branches, like doing merges or pull requests, they suddenly have to remember: oh in this repository it is main, but in that repository it is still master. Or they have go out of their way to modify decade old repositories, potentially breaking all kinds of behind the scenes CICD stuff. Or they have to go out of their way to revert the default on all systems that they’re working on back to master. In any case, this change is a source of errors and wasted effort for zero net good.

3. It does no good in the real world other than making do-gooders feel good about themselves, and giving a capitalist entity some PR to appear more progressive than they are. We all still have masters, existing slaves are not freed, no historical wrongs of slavery or inequality are righted.

4. It’s a misguided change in this case because the word master in this context doesn’t even have a relationship to slavery. Just like a master degree you may hold, or a master key or a master recording of your favorite album have no bearing on slavery. Note that there are no “slave” branches in git.

5. Finally, in the case of git, master is simply more accurate than main because it carries a nuance (derivativeness) that main does not.

There’s no need for master terminology there

Nobody said there is a need, you could call it foo or bar and it would still work. It just that master more accurately describes what it is. Main for example does not describe a derivative relationship, master does.

Also, master in this context is totally unrelated to slavery so I could also just as easily say that there was no need to replace the existing terminology either. It doesn’t solve any real world problems of historic or currently existing slavery, and it doesn’t make anyone’s life better. The only reasons why it was done were appeasement and virtue signalling.

Is it not the main working branch

No it is not. On large distributed projects for which git was designed, you typically don’t directly work on main/master but you create a working branch to do your changes, and when they are ready you merge them to main/master.

There are many types of git workflows, but main/master usually contains the code that is deployed to production or the latest stable release and not some work in progress.

When you start a new project, do you open a new branch or create a whole new repository?

You have to define “project” for that.

• Is your project a change to existing code -> new branch, merge to main/master when done
• Is your project something new that stands entirely on its own? -> new repository

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 …

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.

deleted by creator

There are basically four positions you can take about this:

1. Jesus existed and was crucified
2. We can’t know, because there is no conclusive evidence, but I think (1) is more likely
3. We can’t know, because there is no conclusive evidence, but I think (4) is more likely
4. Jesus is a myth

I am on (2), as are most historians, and you put yourself on (1).

if it’s good enough for the majority of historians

It isn’t. Historians would love to have independent evidence of the existence and crucifixion of Jesus, but there isn’t… so most historians refrain from taking a position one way or the other. The ones that do have to make do with what little objective information they have, and the best they can come up with is: well because of this embarassing thing, it’s more likely that he did exist and was crucified than that he didn’t, because why would they make that up?

That’s rather weak evidence, and far from “proof”.

Not sure why you’d need more

Well for one because the more prominent people who have studied this have a vested interest in wanting it to be true. For example, John P. Meier, who posited this criterion of embarassment that I outlined in my previous comment, isn’t really a historian but a catholic priest, professor of theology (not history) and a writer of books on the subject.

There was a guy named Jesus that was crucified by the romans and all that. There is proof of that

There isn’t actually. The proof is basically: it’s embarassing that their cult leader got painfully crucified, so the early Christians and writers of the new testament wouldn’t have made that shit up.

Personally I find it rather unconvincing.

Where did I say that censorship does not happen?

You didn’t, I got your comment mixed up with what someone else said on another comment chain, and I apologize.

I am one of the victims of the censorship you say doesn’t happen, so I am banned on lemmy.ml for making a comment about the Tiananmen Square massacre.

replied to the wrong comment

Those communities should be urged to move away from lemmy.ml.

Removed by mod

You need to turn on ambient occlusion. That should fix it.

People have choices. If they want to keep using the Lemmy.ml community, that’s their freedom. The alternatives exist, if they want to switch, they can.

Because network effect is a thing, it’s really the illusion of choice. When a lemmy.ml community has 50k subscribers and the equivalent lemmy.world or programming.dev community has just a tenth of that, it’s not really a choice. People will always gravitate towards ml and the smaller community will never gain critical mass unless some strong enough outside force influences that decision.

Which brings me to …

Intrigued by your name change, you are really pushing for this.

I think defederation from lemmy.ml together with raising awareness about ml should be the outside force to move communities off lemmy.ml.

If human skin was sometimes completely patterned

If?

Gingers would like to have a word with you.

It’s not even about which view is right or neutral. On .world posts and comments critical of the US aren’t mass censored like .ml does with posts critical of China, Russia or the former USSR.

The thing is, as far as users and communities go lemmy.ml is pretty much a general purpose instance like lemmy.world, but it is controlled by political extremists who are using their admin position to put their thumb on the scale to push discussion in a certain direction.