apt

“apt supports multiple repositories and you can add your own.”

“"apt-get" is what you use when you want a stable interface (especially scripts)”

“Linux package managers like debian/apt also ship hundreds of signed NPM packages”

“go to pacman/apt and boom everything is right there”

“the package manager I use has not been infected in over a decade”

“It was a breath of fresh reasonability when I found out that apt intentionally uses only HTTP”

“Running apt upgrade or dnf upgrade can render your system unbootable if you're unlucky”

“apt/dnf scripts run on packages a maintainer signed and a distro gatekept”

“I'm honestly a bit disappointed in how apt refused to embrace/support both the container and AI/GPU aspects of computing.”

“we're still pretty far away for apt/yum/pacman installed packages”

“package manager can brick your system at any time because there are literally no safety mechanisms”

“On debian, installing tools should be as simple as ‘apt install’”

“you have to remember which of the several different package managers each specific system uses”

“It won't randomly eat your bandwidth on a metered connection or reveal your OS details to a public hotspot.”

“apt purge software on Debian does a pretty good job of that”

“I just use apt, been doing it for 20 years, it works great.”

“Nix is just another chef, ansible, cfengine, apt, pacman”

“I want my development tools to use my operating system’s package manager.”

“Apt is fine for local development, but it's a bit of a disaster for portability and reproducibility.”

“Using your OS' package manager IS C's package management.”

“Alternatively, you could do development in a container and use apt-get there. That's probably safest now that we're using coding agents.”

“The APT protocol and structure being a bit "dumb" (for better or worse) requires you to fetch files (many of them) in the reverse order they are created”

“we always ought to prefer apt, dnf, over the likes of curlbash, brew, npm”

“It knows what files it puts where and can cleanly upgrade and uninstall with a predictable and standardized method.”

“Meanwhile, 99% of my Linux software is "apt install foo" and that's it.”

“I remember it had a particular fondness for deleting old kernel versions, failing to install the new kernel, and thus bricking the system on boot.”

“Setting up `apt` to pull from a different repo (to say install firefox.dpkg instead of snap) requires like 3-4 commands which are easily searchable.”

“I'd take a standard apt repo over containerized desktop apps any day.”

“I don't think I've seen any similar issues since, across what must be many millions of apt runs”

“I have never had a segfault with APT. Not a single time.”

“obsession of rewriting tools that actually work for many years without bigger issues”

“Porting to Rust therefore a) addresses memory safety, b) gives a chance to attract new developers”

“the tool supposed to solve dependency hell—creating its own dependency crisis”

“I've been using apt regularly on Debian for a long time and never seen it crash or segfault.”

“I think the best move would have been to announce deprecation of those ports separately.”

“This is breaking support for multiple ports to rewrite some feature for a tiny security benefit.”

“This seems like a long window, given to ports to say, "we are making changes that may impact you, heads up."”

“For upgrading a single package, just do "apt install $PACKAGE". It is the same command as for installing.”

“it is probably a relic of the past left there for compatibility reasons and you probably shouldn't use it”

“It's a pleasant surprise to hear that it already does something like this!”