Hi, In the last few days there have been several discussions about Debian's Stable kernel and how it may be too old for newer computers. In a few weeks I'm going to face this problem myself: I'm going to build a secondary system based on a B550 motherboard and the Ryzen 5700G CPU.
My point being that "testing" is kind of a misleading name for this branch of Debian. I find it to be far more stable than Fedora, Arch, or basically anything ...
Debian is not intended as a distro for end users, it's a development branch. Does that mean I shouldn't use Debian Unstable (or Testing) for my home PC as I'm not a developer? I thought Debian Unstable was just a reference to mean it has unstable packages. 0 comments.
If by "safest" you mean "least likely to break randomly," then Ubuntu wins. Ubuntu's packages go through a long pre-release testing process before the final release, to iron out most of the kinks. Debian packages enter Testing after 10 days or less in Unstable, which is not a long time to iron out kinks. 5. level 2.
Debian testing seems to be the best alternative right now; packages are pretty up-to-date and stable too. Moreover, I have more availability of binary packages than I do in Arch where more often I need to compile a package from AUR which is pain due to my underpowered laptop.
sep76. · 2y. Yes testing is a great daily driver. The testing security team tries to push important stuff quick from sid to testing. But i would reccomend using bester until some months after release. Since right after release there is a periode where everyone goes a bit craqy with large updates after the freeze. 9.
Debian Stable always upgrades smoothly to the next Stable release. No reinstall necessary. It's part of the Stable experience. My understanding of Testing (I always stay on Stable) is that once the dev team reaches the point in the cycle where they freeze the software for the next Stable, Security updates also stop or are less frequent to Testing until it is the next Stable.
Testing is the worst of them. The way Debian works, testing gets packages updated only after a 10 day waiting period from being on unstable (Sid). This is important because that means that if a bugged package makes it into testing, it could be months before that package gets to a point that it can go from unstable to testing.