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.
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.