this post was submitted on 07 Mar 2024
691 points (98.1% liked)
linuxmemes
21251 readers
1527 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
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!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Debian is not all about "stability" in the sense of "doesn't crash". Debian is all about consistency. The platform doesn't change. That means if there is a bug that crashes the system for you... it's going to consistently be there.
For me, it was when stable was on kernel 3.16, and 3.18 was in testing, but the latest kernel was 3.19. And this was an era where AMD's drivers not fully OpenGL compliant yet. Which meant games would crash. And knowing "this game will always crash until 3 years from now when we finally get a newer kernel" was enough to chase me off.
debian's neovim package is 0.7.2. Sid is 0.7.2. Experimental is 0.9.5... If there are any bugfixes between 0.7.2 and 0.9.5 that are critical for your workflow... too bad. If its not a "security" release, its not getting updated. You can live with knowing the bug.
"Never change anything, stick to known good versions" only works if you know 100% that the "known good version" is actually bug free. No code is bug free, so inevitably the locked down versions in Debian will have still some flaws (and debian doesn't backport bugfixes, they only backport SECURITY fixes). For most use cases, the flaws will be minor enough to not matter. But inevitably, if a flaw exists, it affects SOMEONE.
If you actually want to do any sort of complicated computing, debian is not a great choice. if you want a unchanging base so you can run a web browser and processor, I'm sure it's great.
Yes, that's what 'stable' means.
Most people use stable to refer to something that doesn't crash or cause issues. Something that you might call "rock solid" which implies it's not going to fall over. Something to put on your server because you'll get great uptime without issues.
Debian is one of the few places where stable might crash more than unstable, because known bugs in Debian don't get backported unless they cause security issues.
I use Debian on my servers because "some testing" is nice and the only thing I run on my servers is docker. And ironically, I have to use a PPA for docker.
So for me, it's a stable enough base OS, but it "too stable" for anything that actually runs on the servers.