• data1701d (He/Him)@startrek.website
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 days ago

    Honestly, in the age of Flatpak and containerization (as well as Debian often being well-supported by upstream projects for script or package-based install), I feel like the age of Debian packages isn’t that annoying anymore; anything important gets security patches, and it’s easier than ever to use 3rd party software without breaking your system. I will add that Debian seems to be much better these days at making sure either a reasonably up-to-date version ships with a release (and can be kept secure during a stable cycle) or not shipping it at all as to allow the user to install it themselves.

    I remember back in just 2021 when it took months after Firefox ESR 78 went EOL for them to update Bullseye to 91; recently, it only took them a few days after 140’s EOL to switch to 153 (and 91-115 and 115-140 happened without much note either), which isn’t perfect, but much better than it was.

    If you need to install it on a new laptop, backports often has you covered. I ran a backports kernel for about a year on Debian Bookworm to get my laptop’s Wi-Fi modem working; I was able to quit using the backports kernel once Trixie came out.

    • nitrolife@hikki.team
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      If you are using only Docker, you don’t need a Linux distribution at all. Just install alpine slim, busybox, or any Kubernetes worker node build.

      Flatpak, much like snap, appimage, and other programs trying to shove old, hole-ridden libraries down my throat under the pretext that “the build is too complex,” is not the kind of software I would welcome on my PC. I’d rather build the application by hand.

      • data1701d (He/Him)@startrek.website
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago
        1. Alpine is still a Linux distro, just a lighter one. Also, busybox is a set of standard utilities as an alternative to coreutils; I have no idea how it’s particularly relevant here.
        2. The thing is, I’m not using only Docker. I also use native nginx as a reverse proxy, for which I like Debian’s defaults, as well as SyncThing, which are both well-maintained packages in Debian. Also I kind of prefer glibc distros. While glibc kind of sucks, so much stuff I like using prefers or requires it; for instance, last I saw, mDNS/Avahi resolution on BusyBox was kind of a pain in the rear.
        3. Most of what I use Flatpak for isn’t network-facing or opening unverified files anyway; the most important applications I do run the native Debian version. Honestly, truth be told, you are correct that I do often prefer native versions and will run the native Debian package if possible (and considering the current age of stable, a lot of them really aren’t that old; Inkscape is basically still the latest version, for instance, while Firefox is always kept to the latest ESR); at some point, though, I do find a Debian package that is too behind to do what I do (though rare, TBH), and despite some issues with Flatpak, at the end of the day, I need to just get a piece of software installed and get on with my day. In that case, I just do a Benjamin Sisko:

        Benjamin Sisko says “I can live with it”

    • eldavi@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      Honestly, in the age of Flatpak and containerization (as well as Debian often being well-supported by upstream projects for script or package-based install), I feel like the age of Debian packages isn’t that annoying anymore; anything important gets security patches, and it’s easier than ever to use 3rd party software without breaking your system.

      i was pleasantly surprised in 2023 to learn that debian was still king in the server space and precisely because of this – i remember doubting trying debian on my personal hardware because of the age of the packages back around 2004.