4 ms·

That's pretty much the same for the desktop, except you are maybe more often in need of some non-free driver that you have to keep available at hand (eg. on ano

That's pretty much the same for the desktop, except you are maybe more often in need of some non-free driver that you have to keep available at hand (eg. on another USB stick) for when the installer asks for it. I find it simpler to do the initial install with an ethernet cable, and only then install the Wi-Fi drivers (or the Nvidia proprietary driver) using the non-free repository. After installing your desktop environment of choice (eg. KDE), the user experience is very similar to that of Ubuntu, except a bit more barebone (or more minimal, or less bloated, however you say it) and more stable (in the Debian sense of stable; eg. you get Firefox ESR instead of the latest Firefox). I like the stability of it: there are very few updates, and even when there are, I've yet to see one that breaks something. That being said, I wouldn't use Debian on all my desktops: having few updates is not always desirable.

TekMol 5y ago
I wouldn't use Debian on all my desktops: having few updates is not always desirable. "having few updates"?
- sillystuff 5y ago
  If you run Debian stable (or oldstable), you only get back-ported bug fixes, and no new features-- the upstream versions of the packaged software are "frozen" before each new major Debian release. So, you don't get a million updates caused by exactly tracking the upstream. You only get the updates necessary to address bugs. A huge upside of this is that you don't have to worry about breaking changes until a major version upgrade. E.g., some years ago upstream TCL changed its default from blocking to non-blocking I/O. I had to change nearly every TCL script I had to account for this change after dist-upgrading to the new Debian version. It was nice to not have a breaking change like this occur with just some random automated update. If you want Debian + rolling release, there is testing and unstable. But, packages in testing only get security patches when they trickle down-- there is no explicit security patching for testing. E.g., I wouldn't run a web browser or other security critical software from the testing release where it is exposed to the outside world. Probably safer to either run sid/unstable for a desktop, or careful use of pinning. For my own desktop, I've been running Bullseye testing, but pin Firefox back to Buster since it doesn't have any library conflicts. Firefox and Thunderbird are handled differently. These packages track upstream ESR versions in Debian "stable", and the version can change in the course of a stable release.
- Arkanosis 5y ago
  Well, yes; you don't get much to update with Debian, whereas using Arch, for example, you have many updates, very often. Sometimes having many updates is what you want (therefore use Arch) sometimes it's not (therefore use Debian).
  - Jenda_ 5y ago
    I want many updates on my desktop, therefore, I use Debian (unstable) ;-)

TekMol 5y ago

I wouldn't use Debian on all my desktops: having few updates is not always desirable. "having few updates"?

sillystuff 5y ago
If you run Debian stable (or oldstable), you only get back-ported bug fixes, and no new features-- the upstream versions of the packaged software are "frozen" before each new major Debian release. So, you don't get a million updates caused by exactly tracking the upstream. You only get the updates necessary to address bugs. A huge upside of this is that you don't have to worry about breaking changes until a major version upgrade. E.g., some years ago upstream TCL changed its default from blocking to non-blocking I/O. I had to change nearly every TCL script I had to account for this change after dist-upgrading to the new Debian version. It was nice to not have a breaking change like this occur with just some random automated update. If you want Debian + rolling release, there is testing and unstable. But, packages in testing only get security patches when they trickle down-- there is no explicit security patching for testing. E.g., I wouldn't run a web browser or other security critical software from the testing release where it is exposed to the outside world. Probably safer to either run sid/unstable for a desktop, or careful use of pinning. For my own desktop, I've been running Bullseye testing, but pin Firefox back to Buster since it doesn't have any library conflicts. Firefox and Thunderbird are handled differently. These packages track upstream ESR versions in Debian "stable", and the version can change in the course of a stable release.
Arkanosis 5y ago
Well, yes; you don't get much to update with Debian, whereas using Arch, for example, you have many updates, very often. Sometimes having many updates is what you want (therefore use Arch) sometimes it's not (therefore use Debian).
- Jenda_ 5y ago
  I want many updates on my desktop, therefore, I use Debian (unstable) ;-)