I recently took up Bazzite from mint and I love it! After using it for a few days I found out it was an immutable distro, after looking into what that is I thought it was a great idea. I love the idea of getting a fresh image for every update, I think for businesses/ less tech savvy people it adds another layer of protection from self harm because you can’t mess with the root without extra steps.

For anyone who isn’t familiar with immutable distros I attached a picture of mutable vs immutable, I don’t want to describe it because I am still learning.

My question is: what does the community think of it?

Do the downsides outweigh the benefits or vice versa?

Could this help Linux reach more mainstream audiences?

Any other input would be appreciated!

  • tisktisk@piefed.social
    link
    fedilink
    English
    arrow-up
    17
    ·
    2 days ago

    I remain interested in the immutables or atomic distros because I know a lot of smart people that swear by them.

    I also don’t try them just yet because I know a lot of dumb people like me that end up breaking a lot of stuff before quitting them altogether.

    They could be amazing and just not perfected yet or they may be a meme and no one’s proved it outright just yet. Will be lurking this thread either way lool :D

    • chunkystyles@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 day ago

      These distros are great for beginners or less technically savvy. They’re really just harder for people who have been using Linux forever and are very accustomed to the old ways.

    • Kroxx@lemm.eeOP
      link
      fedilink
      arrow-up
      2
      ·
      2 days ago

      Yeah I think atomic is more appropriate but I’m not exactly sure what the difference is?

      • tisktisk@piefed.social
        link
        fedilink
        English
        arrow-up
        10
        ·
        2 days ago

        Immutable = Read-Only Root FS && Updates entire system image rather than individual files
        Atomic = Updates as single transaction (all or no update) && Containerization w/ Rollback capability

        This is quick summary from quick research pls correct where technically wrong.

        • T0RB1T@lemmy.ca
          link
          fedilink
          arrow-up
          12
          ·
          2 days ago

          If we’re asking what people mean when they use those descriptors, then you’re correct.

          However, literally speaking, in this context, immutable only means read-only, and atomic only means that updates are applied all-at-once or not at all (no weird in-between state if your update crashes halfway through).

          The rest of the features (rollbacks, containerization, and immutable meaning full system image updates) are typically implied, but not explicitly part of the definition.

          • tisktisk@piefed.social
            link
            fedilink
            English
            arrow-up
            4
            ·
            2 days ago

            I knew a real wizard would clarify sooner than later. Much obliged and keep up the good work anon!

        • Kroxx@lemm.eeOP
          link
          fedilink
          arrow-up
          2
          ·
          2 days ago

          That makes sense, bazzite is referred to as atomic (that’s what I meant in the above comment about atomic being more appropriate, forgot to add that context though lol) specifically instead of immutable. Bazzite updates like you said and you can always roll back, thank you for the explanation!