Non-goals

Does not have to support the runtime installation of kernel modules. This will prevent the out-of-the-box installation of, for example:

  • Proprietary NVIDIA kernel driver (NVIDIA GPUs must either be new enough to use the open-source kernel modules that can be distributed in-tree, or else use Nouveau)
  • VirtualBox (requires out-of-tree modules; QEMU/KVM probably do a better job anyway)
  • Vendor-specific VPNs that require custom out-of-tree kernel modules that cannot be redistributed with the kernel due to license incompatibility

Does not have to support the use case of developing low-level system components like the kernel, drivers, systemd, etc., as this can be troublesome with an immutable base OS.

Does this part mean there will also be no support for ZFS?

    • lnxtx@feddit.nl
      link
      fedilink
      English
      arrow-up
      4
      ·
      20 hours ago

      Neutral. I’m just curious how it will work. Comparing with Debian/Ubuntu as a base.

      • megane-kun@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        9 hours ago

        For whatever it’s worth, I use (up until fairly recently) KDE Plasma on Arch, and it’s pretty much fine. There’s some hiccups especially after a big update such as KDE Plasma 6, but it’s a smooth ride so far.

        If the KDE Plasma developers support an Arch-based distro of their own, and package stuff for this distro with care, I think it’d be a better experience, but I am guessing not by much compared to KDE Plasma on base Arch.

      • Justin@lemmy.kde.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        10 hours ago

        Debain/Ubuntu are always a little behind on library and Qt versions etc. For example with KDE Neon on an LTS they had to overlay/patch many libraries which ended up breaking most of the Qt applications that users could install from the Ubuntu repo. Arch is almost always up to date with the latest stable releases of libraries and Qt making it an ideal base for KDE Plasma which is a fast moving desktop.

        • beleza pura
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          6 hours ago

          Arch is almost always up to date with the latest stable releases of libraries and Qt making it an ideal base for KDE Plasma which is a fast moving desktop.

          are you involved in this project? i have a little bit of a gripe with this approach. unless your idea is to aim this os at enthusiasts instead of the general public, the user should not have to worry about large upgrades that might leave the system in a broken state. this is why debian is always a little behind: making sure a bunch of different components in a million possible different combinations all work well together is hard work and it takes time. i’m not even saying it’s not possible to use a rolling release model and have a user friendly distro (opensuse tumbleweed does it pretty well), but reliability comes before software recency imo.

          edit: btw this is why i said i’m unsure making an os is the job of application developers. what’s ideal for the developers might not be ideal for users.

          • Justin@lemmy.kde.social
            link
            fedilink
            English
            arrow-up
            1
            ·
            6 hours ago

            Yes I am involved in the project. As for not worrying about large system upgrades, things break, no matter how much testing you do on them. For running KDE I prefer to run the latest, it has the least bugs and the newest features.

            There will be at minimum 3 editions of this OS, one for developers and those who love to live on the bleeding edge, one for enthusiasts and one for general users. The one for general users will be well tested and aim to have zero showstopping bugs.