There are some specific complaints I have about technical choices for Debian, like the way daemons autostart post install. But these complaints are outweighed by the benefits of using a distro with coherence across packages and upgrades.
Apt is also just such a phenomenal package manager. It is fast out of the box, and supports some relatively tricky scenarios—like using stable for your system, but a newer Nginx from backports. Feels like I can get the newer features for the one or two packages that I really care about, and then use something stable and boring for everything else.
> Apt is also just such a phenomenal package manager. It is fast out of the box,
This wasn't always the case. There's a good reason almost all guides first written before 2015 specifically instructed everyone to use 'apt-get' directly. For quite some time the more uniform 'apt' frontend really wasn't intuitive or helpful. (Just to be clear: these days it is phenomenal in its simplicity and clarity.)
And as someone who has has to dive in to the package managers' code bases, the overall quality of libapt used to be .. questionable. Figuring out code and control flows back in 2010 was like trying to rub chili out of your eyes with an unsanded wooden spoon.
But the sheer bullheaded stubbornness Debian imposes on their package universe and its architecture means it's an absolute joy to work with if you're doing any kind of distro customisation work.
from apt(8):
SCRIPT USAGE AND DIFFERENCES FROM OTHER APT TOOLS
The apt(8) commandline is designed as an end-user tool and it may change behavior between versions. While it tries not to break backward compatibility this is not guaranteed
either if a change seems beneficial for interactive use.
All features of apt(8) are available in dedicated APT tools like apt-get(8) and apt-cache(8) as well. apt(8) just changes the default value of some options (see apt.conf(5) and
specifically the Binary scope). So you should prefer using these commands (potentially with some additional options enabled) in your scripts as they keep backward compatibility
as much as possible.
https://manpages.debian.org/bookworm/apt/apt.8.en.html#SCRIP...So I don't know what tool other than apt-get could "guides first written before 2015" use.
OTOH aptitude is, to this day, a joy to use.
What do you mean?
But it's a small issue compared to the mess I see in the rest of software these days ...
Alpine Linux seems interesting too, although right now Debian suits me well. I guess the problem is that I still don't make Debian packages myself, while Alpine's APKBUILD seems more approachable -- pure shell, while Debian has an array of tools and formats.
But Debian "lagging" a bit can be a feature, not necessarily a bug.
This can be configured with service-policy.d(5), see https://packages.debian.org/bookworm/policy-rcd-declarative-... for example.
What are you getting conflicts on? Unless you’re pulling from Sid, and did something fun like upgrading libc6, you shouldn’t see version conflicts if everything was installed via apt.
Debian does have Conflicts package metadata - https://www.debian.org/doc/debian-policy/ch-relationships.ht...
So in theory I don't like it, but I now better understand the possible reasons for it, and I haven't run into it recently
I think there is room for other systems that don't have this problem, but Debian is good at what it does, and you can build other things on top of it
It grew on me after a long time. I always thought it was not the most "technically sound" way of doing things
i.e. I don't really like the packaging model of global updates where you don't know what's going on, and sometimes there are version conflicts
But I have come to appreciate the stability and good intentions of the Debian project
Sometimes it's not technical excellence that matters the most, but the purpose and goals of the project