this post was submitted on 14 Jul 2025
405 points (100.0% liked)

linuxmemes

26258 readers
67 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 98 points 2 days ago* (last edited 2 days ago) (8 children)

    It's a retroactive bastardization of the word based on one particular culture's one particular interpretation of it (master being, apparently, a slaveowner) that ignores both the much earlier meanings of master artisan or master craftsman (as opposed to journeyman and apprentice) and masterpiece (through which an artisan is recognised as a master), and the modern meaning of a master copy (like a master record in disc printing).

    This isn't like replacing the "master and slave" terminology with regard to connected devices. That one was warranted because it was often inaccurate and confusing. But forcing the adoption of main instead of master feels like someone got offended on someone else's behalf because a word looked superficially like that other bad word, and apparently we can't have an understanding that goes deeper than what letters it's made up of.

    Amerika ist wunderbar. This is an --initial-branch=master household.

    [–] [email protected] 25 points 2 days ago (4 children)

    regardless of that, it's never inconvenienced me and it's still a net gain in readability, since main actually means what it means. have my shell scripts set up to use either one for any repo I'm in automatically.

    [–] [email protected] 25 points 2 days ago* (last edited 2 days ago) (3 children)

    Honestly it's not even about convenience. As far as breaking conventions go, this one has none-to-minimal impact -- existing master branches won't suddenly become invalid. But it's yet another instance of a subset of a subset of a subset of users getting to enforce their sensibilities for superficial reasons, and ultimately with zero effect regarding the cause they claim to represent; cultural and linguistic differences be damned.

    I'd love to be more specific, but I don't want the comments to turn into a warzone.

    And don't pretend like master doesn't mean what it means.

    [–] [email protected] 24 points 2 days ago (1 children)

    And don't pretend like master doesn't mean what it means.

    Claiming that master on github stems from master recordings is not only disingenuous but also incorrect.

    As a FOSS alternative to BitKeeper, Git naturally reimplemented it's naming conventions as well - and because of the power of version control - we can actually check what the original meaning was derived from:

    We are then going to modify the file on both the master and slave repository and then merge the work.

    And yes I agree that GitHub just changing the name of the default branch while keeping their ICE contracts is performative as fuck - which imo means we should both boycott GitHub and use naming conventions that don't have a history related to one of the worst atrocities the global north has brought upon the world...

    [–] [email protected] 11 points 2 days ago* (last edited 2 days ago)

    I concede the point about the word's origin... not that I've seen anyone ever refer to a branch as a "slave", nor do I think that it's appropriate given that the branches are not subservient to the trunk/master/main/etc until one is merged into or rebased onto the other...

    I also wrote a whole-ass speech about the modern world's relation to the Atlantic slave trade and the guilt certain people are trying to inflict on everyone, but I know what the replies will be (we're just redditors by another name after all) and it's ultimately not a soapbox worth dying on. Anyway, my thesis is study history, learn its injustices, and learn how to do better effectively.

    load more comments (1 replies)
    load more comments (1 replies)
    load more comments (4 replies)