I'm naming my production branch goshujin-sama
this post was submitted on 14 Jul 2025
399 points (95.9% liked)
linuxmemes
27012 readers
1089 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
sudoin 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 figures
We 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
"Obey your master! Master!"
Imagine darth vader calling palpatine main
load more comments
(1 replies)
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)
live / staging / dev
both. but majority are master cause that's the default and I'm too lazy to change nor do I really care.
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.
I use master in all my projects
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
load more comments
(1 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.
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.
Calling an original, analogue recording a master does make sense, as all copies of it will by nature be of a lesser quality. This isn't the case for git branches tho.
I don't think the word "master" is indicating quality though, just that it's the "source" or "basis"
load more comments
(1 replies)
mainline
Zeus