this post was submitted on 31 Jan 2024
1521 points (97.3% liked)
linuxmemes
21611 readers
1281 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 members of the community for any reason.
- 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.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
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. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
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 fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'll reply to myself to avoid editing the above (for transparency).
Linux users in this post: think on all issues that you had with your system. Bugs, papercuts, devs assuming use case, regressions (shit stopping working), dependency hell, anything. How many of those issues apply to the kernel, in a way that you can say "the kernel devs fucked it up"? For me, never.
I have a hypothesis, that I do not know the truth value of, that the kernel not annoying the shit out of us users is directly related to Torvalds' propensity to tell people "your code is GARBAGE", instead of sugar-coating it. And that free + open source projects where project leaders don't do this tend to be crappier. (Does anyone here know a good way to falsify this hypothesis?)
It's half this, and half an explicit policy "we do not break user space". Together it meant that if you did anything that screwed up the user space you got told about it at length.
Now Linux culture is established enough that it only really needs the policy, and not the cussing people out to enforce it.
Famous email about it here: https://linuxreviews.org/WE_DO_NOT_BREAK_USERSPACE
I wasn't aware of that email, only the quote itself.
...not gonna lie, I think that it was beautiful. I have my bones to pick with pulseaudio but come on, you don't shift blame like this, the guy deserved some smacking.
On-topic: I have my doubts if policy is enough to enforce it, or at least to enforce it in an efficient way.
Well this is it. What really enforces the policy is rejecting commits that break user space.
Now if you've got a large enough group of devs, rejecting commits is fine, but if you've only got a small group you need everyone to be working productively, and you can see why Linus ended up giving angry feedback about commits that were wasting everyone's time.