Hacker News Reader

Comment by _jal | Hacker News Reader

That's my experience, too. I have nothing against Ubuntu, but when I've had issues with it, they're always... some Ubuntu addon to Debian, and it turns out that I don't care about whatever feature that is. So last time I had reason to reinstall the OS for the main desktop machine, I just went back to Debian. Haven't had any regrets.

(All of my experiments with Docker/K8s/Terraform/etc. are running on VMs under FreeBSD/BHyve, another OS I'm solidly back to loving after being distracted by shiny objects, but that's a different story.)

View on HN

I’ve had numerous colleagues pitch Debian testing for desktop as stable has absolutely ancient packages. It’s never worked as well as Arch.

This is the new stack:

    Desktop/Laptop: Arch
    Server: CentOS/Amazon
    Small footprint: Alpine

I’ve had my Arch install for 5 years and it still works with no issue. Latest packages, runs like a dream.

It's better to use Debian Unstable because Testing doesn't get timely security updates.

Unstable (aka Sid) rarely lives up to its name, having ran it as my daily driver for a few years. Comparatively, the months I spent on Arch were marred by packaging issues resulting in me switching back to Debian.

I want the maintainer to hold back an update and write patches when there are noteworthy regressions that hurt my workflow. The Debian package maintainers consistently act in my best interest, not that of the developer's or outside political interests. Turns out I find that really useful.

Debian Unstable is the base for Ubuntu.

It's not unstable at all.

The "unstable" there means that everything changes all the time. It does not mean that things break (although they do break way more often than stable - when I tried it, I did have to reinstall the OS every few years).

I was under the impression that `unstable` is... well, not stable (that it breaks). Is it usable for someone who doesn't want to spend much time fixing the system?

In Debian 'unstable' means that the package versions installed aren't stable. That is, there is a high level of package churn just like any rolling release. It isn't any more buggy/crash prone than any other rolling release. There is just a risk at running bleeding edge vs. vetted/known working software.

Docker makes the base OS largely irrelevant for testing in my workflows.

Reply on news.ycombinator.com