NixOS’ influence and importance at pushing Linux forward into the (previously) unexplored landscape of configuring your complete system through a single config file is undeniable. It’s been a wild ride, but it was well worth it.

And although it has only been relatively recently that it has lost its niche status, the recent influx of so-called ‘immutable’ distros springing up like mushrooms is undeniably linked to and inspired by NixOS.

However, unfortunately, while this should have been very exciting times for what’s yet to come, the recent drama surrounding the project has definitely tarnished how the project is perceived.

NixOS’ ideas will definitely live on regardless. But how do you envision NixOS’ own future? Any ETA’s for when this drama will end? Which lessons have we learned (so far) from this drama? Are there any winners as a result of this drama? Could something like this happen to any distro?

In case you’re out of the loop. Though, there’s a lot that has transpired since but which hasn’t been rigorously documented at a single place; like how 4 out of 5 NixOS board members have quit over the last 2 months or so.

  • GolfNovemberUniform@lemmy.ml
    0·
    4 months ago

    So, “disabling immutability” therefore only applies to ‘hacks’. Right?

    Idk if everything can br called “hacks” but mostly yea.

    (and also how ~/.local/share/themes could be utilized for this)

    I know but idk if GUI apps and extensions can see themes installed in ~/.local and how many installation guides tell about that method.

    Fedora Atomic’s new OCI-enabled model does allow this.

    Idk how it works and how simple it is but gtk that.

    Fact of the matter and the issue at hand is that traditional distros don’t deal with issues like these. Right?

    Exactly.

    Similarly, ‘immutable’ distros are not to blame if a new user breaks their not newbie-friendly ‘immutable’ distro.

    But we’re talking about situation when user-friendly distros become immutable. If the user willingly chooses an advanced distro, it’s not the distro’s fault but, for example, you said that Fedora expects their immutable options to become mainstream. I know that Fedora and other immutable distros are often recommended for new users now. This means that the ones that recommend them consider them user-friendly. Imo this, as well as rumors about Canonical want to make Ubuntu Core the default desktop offering, destroys your point in the context of this discussion.

    Do you think I understood you correctly?

    Yes that’s exactly what I’m talking about.

    The expression “during runtime” is used to express a running and/or currently in use system. So, if my device is off, then the expression “during runtime” does not apply. When I’m using the system or even if it’s just idling, then the expression “during runtime” does apply. However, it’s possible with Btrfs (and more sophisticated technologies) to create a partition/deployment/image on your disk that’s currently not running nor in use and which has some changes compared to your running system. Then, once again, the expression “during runtime” does not apply.

    Thank you for the explanation. I appreciate it. And in this case I think my definition of immutability applies to these “runtime-immutable distros” too.

    Only after the (soft-)reboot will I be able to use Emacs; be it through the console/terminal or find it in the app drawer.

    Another (but small) confusion point for new users.

    The crux of this conversation lies here I believe. Your notion/understanding of an immutable system is probably more correct and more in line with what you’d expect from its name. However, the name “‘immutable’ distros” is unfortunately not descriptive. Contrary to what you’d expect, it’s not a distro that happens to be an immutable system; at least, not in the absolute/complete sense.

    I understand it.

    And, to be honest, I’m not sure if you answered the bold question.

    Idk what to answer. Full or partial immutability, it still creates the same issues I described.

    • bsergay@discuss.onlineOP
      0·
      4 months ago

      Thank you for being patient with me! And thank you for yet another set of clarifications!

      Idk if everything can br called “hacks” but mostly yea.

      I’ve used the term ‘hacks’ a couple of times without properly defining it. My bad. So, I’ve used it in the context of “doing things the unintended and/or unsupported way”.

      but idk if GUI apps and extensions can see themes installed in ~/.local

      They should.

      and how many installation guides tell about that method.

      Arch wiki states it and there’s no reason (in this case) to assume it won’t work. Furthermore, FWIW, the documentation on uBlue does discuss theming.

      Idk how it works

      Currently, it involves creating your own image :P .

      and how simple it is but gtk that.

      So, as just mentioned, it’s possible. But, it’s definitely more cumbersome than placing it in /usr/share/themes.

      But we’re talking about situation when user-friendly distros become immutable.

      Are you referring to distros like Linux Mint, Pop!_OS and Zorin becoming immutable? While it’s definitely possible that I’ve alluded as such, I can’t recall it. Nor was I able to find it in my earlier writings. Could you explicitly state what you mean by this and when I’ve (at least) hinted at this?

      but, for example, you said that Fedora expects their immutable options to become mainstream.

      If, by becoming mainstream, you mean that over half of Fedora’s user base will be using them, then yes.

      I know that Fedora and other immutable distros are often recommended for new users now.

      If you meant uBlue images with “other immutable distros”, then I’m fine with this statement. However, if you meant other immutable distros, then I’d like to know which ones you meant. Furthermore, even Fedora’s own images are rarely recommended to new users. Generally, at least from what I’ve seen, Aurora, Bazzite and Bluefin (all three being uBlue image) are mentioned in these conversation. And, IMO, rightfully so.

      This means that the ones that recommend them consider them user-friendly. Imo this, as well as rumors about Canonical want to make Ubuntu Core the default desktop offering, destroys your point in the context of this discussion.

      Sorry. I lost you here. My bad. What’s my point in the context of this discussion?

      Another (but small) confusion point for new users.

      At least the terminal output makes it very clear that a (soft-)reboot is required. I’ve honestly never seen anyone mention this, i.e. the need to (soft-)reboot for the changes to take effect, as something that leads to confusion. I do understand the frustration that follows from the act of (soft-)rebooting though :P .

      Thanks once again for another lovely set of clarifications! Thank you in advance!

      • GolfNovemberUniform@lemmy.ml
        0·
        4 months ago

        Tbh I am not sure anymore if you’re being serious in this discussion or just trolling because I explained some things very clearly but you still misunderstand them a lot. I’m not willing to continue this. I apologize if I’m not right but I have to stay away from trolls and other kinds of evil people.

        • bsergay@discuss.onlineOP
          0·
          4 months ago

          Unfortunately, you’ve yet to respond. Therefore, I was unable to verify everything mentioned below. Regardless, for the sake of completeness, I would like to give a brief overview of our interaction and how I have perceived it.

          My intent regarding this conversation:

          • Reach a common ground on our understanding of the topic at hand. Like, what even is an ‘immutable’ distro.
          • Highlight how the basic notion of an ‘immutable’ distro’ encompasses a wide variety of distributions that differ from each other more than traditional distros do.
          • Understand why, despite acknowledging the importance of implementation, you still believe it’s inconceivable for future implementations to overcome current shortcomings.

          However, we weren’t able to get that far. This is IMO primarily due to the following:

          • Abrupt end of the conversation by you. This is basically the reason.
          • Your misrepresentation of yourself. I accurately point towards the pain point. However, you -for some reason- deny it or accuse me of intentionally misunderstanding. However, eventually; like a few comments down the line, you accept my earlier found pain point. This just makes conversation take way longer than it has to. Like when I rephrased your understanding of ‘immutable’ system to one in which some directories are immutable. You first accused me of misunderstanding, but later used partial immutability yourself.
          • Your use of words, phrases, and sentences without recognizing the need for definitions. When later prompted to give definitions, you’ve failed spectacularly at giving complete and/or sufficiently clarified ones. This prompts me to ask for clarifications, and the cycle continues… I believe this stems from your lack of familiarity with the subject matter. Like how I had to explain to you what runtime is. A word which is used in the actual definition of ‘immutable’ distros.

          The points you actually raised to discredit ‘immutable’ distros:

          • Unfit for old PCs and/or HDDs. Answer: This is related to implementation. You even agreed to this when you noted yourself that this is not an issue on NixOS. So, busted.
          • Different workflow compared to traditional distros. Answer: I don’t quite recognize why this is a problem. The workflow on the very first Debian is different from how it’s today. Does that make Debian’s current iteration bad? No, obviously not. Similarly, it being different is not inherently a wrong/bad thing. So, again, busted. The important part is documentation/guides/tutorials that facilitate the needs of people that intend to switch and/or try it out. Which brings us to…
          • Lack of resources. Answer: This doesn’t make it inherently bad. It just makes it harder for users to learn how to interact with the system. And, again, this continues to improve as the user base becomes bigger. When I made the switch (over two years ago), resources were abysmal. However, today, projects like uBlue have produced good documentation for its users. And it will only ever improve. Yet, again, busted.
          • Tampers tinkering. Answer: In the absolute sense; no. There’s only very little you can’t do on current ‘immutable’ distros. And there’s active effort to work those things out. So, it’s related to implementation and/or maturity. It’s also not clear what prevents a future implementation of an ‘immutable’ distro to be interacted with exactly like how we interact with traditional distros. Consider looking into stuff like systemd-sysext if you want to see a glimpse of what’s yet to come. Thus, this point is also refuted.

          There is perhaps a lot more I could go over, but I’ll suffice with this for the sake of brevity.