• Guenther_Amanita@feddit.de
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    edit-2
    1 year ago

    Did you even read the article? You definitely should!
    I did, and especially the “flexibility”-argument should change your mind.
    Just look at NixOS for example. It’s just as configurable as Arch (from what I’ve read), but immutable. And it’s also not more complicated, just different.

    Immutable OSs only restrict you as much as you want them to be.


    Also, the underlying technologies (like OSTree, nix-config, A/B-Root, and so on) aren’t proprietary.
    Just look at uBlue, they’ve utilized OSTree to share system configs.


    While some things really just aren’t possible anymore or require workarounds, it opened the door for many, way more interesting routes.


    Also, you don’t need to be angry.
    Nobody will take anything away from you. Mutable distros will still persist for many many years, maybe forever?

    We should be exited what the future brings!

    • TCB13@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      1 year ago

      Yes I did, the article is very well written and effectively debunks a lot of misconceptions however those distros are still an unnecessary extra step that don’t provide a sufficient gain / improvement over “mutable” distributions and/or properly done setups.

      “just different” is by definition “more complicated” as most people going on the “immutable” hype will have to change entire workflows and tech stacks to end up gaining nothing. Moreover immutable distributions (or the majority / most popular of them) will simply add a ton of extra engineering hours and you can’t debug/fix things as quickly as you would otherwise will.

      As the article said security isn’t even a valid argument for immutable distros and I’ll give you even more reasons. Properly done setups run on container technologies that allow for a more decent way of immutability - typically snapshots. If you’re going bare metal then use ZFS / BTRFS instead of the Ext4 crap and will also be provided you with that. Snapshots can be easily made automatically on schedule, manually, moved between systems etc. and won’t get in the way of your developers.

      Also, the underlying technologies (like OSTree, nix-config, A/B-Root, and so on) aren’t proprietary

      True, but this hype is much like Docker and it will invariably and inevitably lead people down a path that will then require some proprietary solution or dependency somewhere that is only required because the “new” technology itself alone doesn’t deliver as others did in the past.

      As with CentOS’s fiasco or Docker it doesn’t really matter if there are truly open-source and open ecosystems of immutable distributions because in the end people/companies will pick the proprietary / closed option just because “it’s easier to use” or some other specific thing that will be good on the short term and very bad on the long term. This happened with CentOS vs Debian is currently unfolding with Docker vs LXC/RKT and will happen with Ubuntu vs Debian for all those who moved from CentOS to Ubuntu.

      We had good examples of immutable distributions and architectures before as any MIPS router and/or IOT device is usually immutable and there are also reasons why people are moving away from those towards more mutable ARM architectures.

      We should be exited what the future brings!

      We don’t need to see the future to understand what immutable OSes bring to the table - we just have to look at the shit show that was made around MIPS.