edit: WHICH ONE OF YOU FUCKING MEMELORD FOUND MY ADDRESS AND SENT ME THIGH HIGHS AND CAT EARS?

    • Buffy@libretechni.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 hours ago

      Cachy is Arch based so unless you really want to customize your system its not worth switching IMO as you’re likely already receiving the Arch benefits.

  • Gonzako@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    14 hours ago

    I do use an arch-based distro tho I’ve never like gotten the bad sides? Maybe my distro maintainers are just that good

    • 1984@lemmy.today
      link
      fedilink
      arrow-up
      5
      arrow-down
      2
      ·
      13 hours ago

      There isnt any bad sides, not really.

      It used to be hard to install but that is also not the case anymore.

      People think its unstable because it has the latest packages. I mean, sometimes i have had issues, sure. A few times, bluetooth stack was bugging out in the newest kernel. Another time plasma had bugs with graphics, which I reported and it was fixed just a few weeks later.

      Nothing that broke the entire system. Just small issues.

      But this is much better than running Debian which has very old packages, full of old bugs. They used to be a full generation behind in plasma for example, and using a kernel that was over a year old. Those things leads to poor hardware support, getting bugs solved over a year ago and so on.

      I really dont understand Debian users because ive never experienced how an updated system is worse than a very old one.

      • rtxn@lemmy.worldM
        link
        fedilink
        arrow-up
        13
        ·
        edit-2
        12 hours ago

        That tells me you don’t understand what a “stable” release branch is. The Debian maintainers do a lot of work to ensure that the packages not only work, but work well together. They don’t introduce breaking changes during the lifecycle of a major branch. They add feature updates between point releases, and continuously release security updates.

        In the real world, that stability is a great value, especially in the server space. You’d be insane to use Arch as a production server, and I’m saying that as an Arch user.

        Something, something, sword of Damocles.

        • 1984@lemmy.today
          link
          fedilink
          arrow-up
          1
          arrow-down
          3
          ·
          12 hours ago

          Well yeah, I wouldnt use it as a server.

          I know Debian is trying to make software work well together but they are still on ancient versions full of old bugs.

            • 1984@lemmy.today
              link
              fedilink
              arrow-up
              1
              arrow-down
              5
              ·
              edit-2
              12 hours ago

              You dont know which version Debian is using of software? You can go check if you actually want to know.

              Then you can take that version and go to bugzilla or whatever bug tracking software its using, and see bugs fixed in newer versions.

      • Qwel@sopuli.xyz
        link
        fedilink
        arrow-up
        7
        ·
        12 hours ago

        I mean, they distributed the xz attack, and then rolled it back when a debian sid user signaled it. This is just not a viable way to do things, especially if the number of users increases. You need a stronger testing policy before the update hits the users, you shouldn’t just assume everything can be fixed by further updates. Debian stable is a bit on the extreme side of that, but Debian testing or Fedora feel much more reasonable long term to me

        • 1984@lemmy.today
          link
          fedilink
          arrow-up
          2
          arrow-down
          2
          ·
          edit-2
          12 hours ago

          Yeah I remember that. It was a very rare event though. For Linux users that want the latest versions, this will happen and there is no way to avoid it.

          We take risks either way. Either by using old bugs or new bugs.

          I think all apps should be much more sandboxed than they are today, but it would require a new way of writing and running apps. We have Flatpak though, its a start.

          • Qwel@sopuli.xyz
            link
            fedilink
            arrow-up
            1
            ·
            11 hours ago

            The old bugs will not send your ssh keys to an unknown network address. If they did, they would get patched or not published. These bugs are known in advance, they are not risks, they are issues. You can make a decision to use them or not, and then you’re set for 5 years. Like, they are both bugs, but they work out very differently if you want to rely on your system.

            The thing is that Fedora or Debian testing (and derivatives) bring the latest version fast-enough for the vast majority of people. They don’t make bugs last longer like Debian stable does. When an app is bugged for two weeks, you encounter the bug one month after Arch users, then you get the fix two weeks later. The total bugged time stays the same, but the risks of something really bad happening is much lower. The downside is being one or two month late, and most people don’t care about this kind of delay. (obviously when bugs are found, it can be much more than one or two months)

            • 1984@lemmy.today
              link
              fedilink
              arrow-up
              1
              arrow-down
              3
              ·
              edit-2
              11 hours ago

              I know from experience its just not just a couple of months if we are talking Debian stable.

              Here is what chat gpt is saying, even though the versions is already outdated:

              Debian Stable lags behind Arch Linux by roughly 1–3 years on most core packages:

              Breakdown by category:

              Linux kernel~6–18 months behindRolling, latest~1 year

              GCC / LLVM / Clang~1–2 major versions behindLatest stable1–2 years

              Python / Node / Go1–3 versions behindLatest stable1–2 years

              GNOME / KDE / XFCE One major release behindCurrent1–1.5 years

              SystemdUsually current − 1Current6–12 months glibc / coreutilsOften within ~1 yearCurrent6–12 months

              Security patchesBackported rapidlyUpstream latest0 delay on fixes

              In practice:

              Debian 12 (Bookworm, mid-2023) ships kernel 6.1, GCC 12, GNOME 43.

              Arch (today) has kernel 6.11, GCC 14, GNOME 47.

              So Debian Stable is about 2 years behind Arch overall, though security backports mean it’s not “outdated” for production.

              • Qwel@sopuli.xyz
                link
                fedilink
                arrow-up
                2
                ·
                10 hours ago

                Yes, Debian stable and testing are two very different things. Testing is essentially a slower rolling release that only takes packages that have been tested in Debian unstable, which is a very fast rolling release. Similar thing with RHEL, Fedora is a quasi-rolling distro that takes packages after testing in Fedora rawhide.

                • 1984@lemmy.today
                  link
                  fedilink
                  arrow-up
                  2
                  arrow-down
                  1
                  ·
                  10 hours ago

                  Yeah. Maybe Debian testing is fine. Couple of months delay is not a huge deal, even though i really want the latest packages myself. When a new version of plasma or gnome is released, im right there waiting for it immediately… :)

  • osaerisxero@kbin.melroy.org
    link
    fedilink
    arrow-up
    29
    ·
    21 hours ago

    edit: WHICH ONE OF YOU FUCKING MEMELORD FOUND MY ADDRESS AND SENT ME THIGH HIGHS AND CAT EARS?

    Ok but how did they fit tho

      • Arkhive@piefed.blahaj.zone
        link
        fedilink
        English
        arrow-up
        5
        ·
        19 hours ago

        Just finished my basic niri install on NixOS. Seriously loving it. Had been wanting to ditch Hyprland for a while, but kept hitting walls with tutorials and blogs trying to convince me to use flakes and home manager. Finally last night I sat down and completely rewrote my config to just be simple default config style and got niri working. Feels like the window manager experience I’ve been dreaming of my whole life.

        • Dran@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          18 hours ago

          What issues were you having with hyperland? I’ve been running awesomewm for about a decade and I know my days on x11 are numbered. Hyperland was going to be my next trial.

          • Arkhive@piefed.blahaj.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            55 minutes ago

            I don’t like the dev. If you want more details I can maybe go find sources, but yeah… I no longer want to support the software.

            And I was too lazy to go edit my config to suppress the donation request popup, so completely refactoring my system was the obvious, lower effort, answer 🤣

        • banshee@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          19 hours ago

          I’m getting ready to do the same thing - just need a couple hours of extra time to take the plunge!