this post was submitted on 13 Jul 2023
58 points (91.4% liked)
Linux
47993 readers
1194 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I personally recommend against using Debian Testing for anything other than testing the next Debian release. It gets slower security updates, and breakages get fixed slower than just using Sid directly. Since Sid has its own securirt team and since it moves faster, breakages are fixed sooner. Even in the official documentation Debian doesn't not suggest using Testing for the same reasons.
While that's true in theory, it's still very common to run Debian Testing on a desktop in practice. For a user coming from Fedora, there would likely be culture shock from the dated packages in Stable. Using Stable with Flatpaks+Nix would be more usable, but OP's experience does not sound like it would fit well with the effort/knowledge required for this solution.
I wouldn't recommend Sid to a less-experienced user and I didn't recommend Arch for a similar reason.
If you don't recommend Sid, then Testing is out of the question. Testing is Sid, but less secure. Testing also has package freezing during the last stages of the release cycle. If you want a stable, and managed Debian, then the latest stable is the answer. If you want an cutting edge, semi-rolling release Debian, then you want Sid. Being in the middle has no advantages to the end user, and only invites complications. If something is broken in Testing, you have to wait for it to be fixed in Sid first, then trickle down to Testing at an absolute minimum. Why add an extra delay for nothing?
EDIT: offcial documentation https://www.debian.org/doc/manuals/debian-faq/choosing.en.html#s3.1.6
Want share my 2c as I prefer testing over sid. It is balance which side you want. Sid got break more freq but also fixed more quickly. Testing has less break but fix also come slowly. For me I prefer less break. So I setup preference/policy to get testing higher than sid. This is not for breakage/fix nor security fix. This is about package available. I think Firefox is one example that testing only has esr so it will install latest from sid and most other packages still tracking testing. Again personal choices and that's beauty of Linux.
While you are always free to make your own choices, this is very bad advice for someone looking to try another distro.
https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian Official documentation again does not recommend mixing multiple releases like this. You would be much better off just running Sid, or Stable then using the Firefox flatpak/snap/appimage for the latest release. Debian is a long term stable distro, so if you want newer packages you are advised by the developers of said distro to just use Sid.
yeah, I agree with you, for anyone new to debian maybe should follow official suggestion. But as user using debian so long, I think I understand the risk (of course the benefit) of my setup. Maybe I will try sid someday. Have a nice day!