• quarterlife@lemmy.sdf.org
      link
      fedilink
      arrow-up
      1
      ·
      7 hours ago

      I disagree with you fundamentally, if it wasn’t for the simple updates and stability this would not have the success that it does. The image is part of the model.

    • j0rge@lemmy.ml
      link
      fedilink
      arrow-up
      4
      arrow-down
      3
      ·
      1 day ago

      lol you’re confusing me, bazzite isn’t immutable. Do you mean to say “Bazzite is growing for other reasons?”

      • fmstrat@lemmy.nowsci.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        1 day ago

        Wut? You’re responding to a trend graph for Fedora’s immutable (Atomic) forks.

        Built on Fedora’s rpm-ostree system, Bazzite uses an immutable design with atomic updates and rollback functionality.

        https://en.m.wikipedia.org/wiki/Bazzite_(operating_system)

        But yes, since the trend chart is showing immutable distros and how Bazzite is growing, I am saying the fact that Bazzite is immutable has nothing to do with it’s growth.

        Edit: Reading again, I realize you might not know that Fedora Atomic is the immutable base. 😉

        • j0rge@lemmy.ml
          link
          fedilink
          arrow-up
          4
          arrow-down
          2
          ·
          edit-2
          22 hours ago

          The Bazzite team doesn’t control the wikipedia page, just the official documentation. Someone made up the term “immutable design”, that’s not a thing it’s just a container. There’s no need to confuse people just call it bazzite or a container. Atomic is a fedora brand name, it’s not a thing to classify things under.

          As you can see from the comments in the thread all this does is confuse people.

          Source: I work on bazzite

          • fmstrat@lemmy.nowsci.com
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            1
            ·
            21 hours ago

            “Immutable”: A term to describe Linux operating systems that do not follow the traditional filesystem layout where every single file can be removed by the user with root privileges. It is more nuanced than this in the case of Bazzite, but is still considered “immutable” from the point of view of the extended Linux community. The Bazzite team would not describe Bazzite as an “immutable” operating system.

            https://docs.bazzite.gg/General/terms/

            I’m a big fan of Bazzite, but as stated in the docs, “immutable” is a term the community uses to describe it.

            Education is the key to reducing confusion, not pretending a system architecture doesn’t exist or matter.

          • j0rge@lemmy.ml
            link
            fedilink
            arrow-up
            3
            ·
            22 hours ago

            Bazzite contributor here, there’s no reason to care about this. This term just confuses people you can safely ignore it.

          • fmstrat@lemmy.nowsci.com
            link
            fedilink
            English
            arrow-up
            0
            ·
            23 hours ago

            Pretend your running a live OS off a read-only USB, yet any changes (app installs, config changes, etc) you make are saved to the HD. A new version of the OS comes out, so you write a new ISO to your USB, and upon booting it, all you changes are applied on top.

            This is a simplistic view of immutable distros, but thwy wrk more like snapshots. It allows for rollback. So you install v1, then v2 is a newer snapshot of the base OS, v3 is another, always building.

            The catch is they often require apps to run under things like flatpak so you don’t have to alter the OS packages. Personally, I’m not a fan for a daily driver, but it’s great for distros like Bazzite.