this post was submitted on 14 Jul 2025
386 points (95.7% liked)

linuxmemes

26254 readers
228 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
     
    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] sunglocto@lemmy.dbzer0.com 9 points 2 days ago (1 children)

    I use master in all my projects

    [–] anarchy79@lemmy.world 8 points 2 days ago (1 children)

    I save my code as .txt files on my hard drive.

    They follow the naming convention "project1", "project1a", "project1a1" and so on in consecutive logical order

    [–] _stranger_@lemmy.world 5 points 2 days ago

    I believe that's called goblin mode (production_code.final(2).txt)

    [–] rozodru@lemmy.world 8 points 2 days ago

    both. but majority are master cause that's the default and I'm too lazy to change nor do I really care.

    [–] smiletolerantly@awful.systems 9 points 2 days ago* (last edited 2 days ago) (3 children)

    Last place of employment had develop as the default branch. Actually quite liked it. (There also was a main branch, which only got merged into as part of the release flow, so might as well have called it release, I suppose).

    Anyway, IMO it communicated "volatile and subject to change" a lot more clearly than things like "head of main" etc

    load more comments (3 replies)

    The real answer is whichever is easiest. If you've got a master branch and it's a pain to switch, then I wouldn't do it. If you've got a badass coder who is disturbed by the terminology, then I'd say to do it to keep the peace. It depends on the situation.

    [–] pelya@lemmy.world 11 points 2 days ago

    I'm naming my production branch goshujin-sama

    [–] ChuckTheMonkey@fedia.io 15 points 2 days ago (1 children)
    load more comments (1 replies)
    [–] VisionScout@lemmy.wtf 8 points 2 days ago* (last edited 2 days ago)

    master.

    I grew up with master before the master nonsense. It's ingrained in me. So i use that in my projects. Some projects i contribute use main, and i don't give a fuck. It just fucks up my memory muscle - but nothing that an alias doesn't solve.

    EDIT: and btw, fuck github.

    [–] RustyNova@lemmy.world 4 points 1 day ago

    Personally I've come to hate main because it breaks habits easily. I'm working 75% of the time on master repos, but then I might need to do a quick edit on a main repo and suddenly my git checkout master doesn't work.

    Or even copy pasting scripts from one project to another can easily break if you forget to change the branch

    The reason behind the change is pretty stupid anyway (I'm against slavery but it shouldn't be treated like a slur still)

    [–] mhague@lemmy.world 4 points 2 days ago (4 children)

    Using master is stupid. Is your branch in charge of others? Is it more skilled than your other branches? Software engineering has too many crusty dorks that stick to their paradigms like it's their religion. Acting like it's their heritage to use outdated terms but also it doesn't matter so that's why they'll keep using it.

    [–] cley_faye@lemmy.world 4 points 1 day ago

    The name have nothing to do with being in charge of others, skill level, or anything, but, sure.

    load more comments (3 replies)
    [–] replicator@sh.itjust.works 9 points 2 days ago (2 children)

    "Obey your master! Master!"

    [–] juipeltje@lemmy.world 7 points 2 days ago

    Imagine darth vader calling palpatine main

    load more comments (1 replies)
    [–] hakunawazo@lemmy.world 9 points 2 days ago

    live / staging / dev

    load more comments
    view more: β€Ή prev next β€Ί