• 0x4E4F@infosec.pub
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      It may be useful for advanced users that just don’t have time to bother with dependency hell… but, that’s about it IMO.

    • MadMaurice@discuss.tchncs.de
      link
      fedilink
      arrow-up
      8
      ·
      edit-2
      1 year ago

      You do realize that updating is a non-deterministic process, right? The entire point of the nix language is to be deterministic. And the only thing these update scripts do is generate new nix code. It’s not like the nix part of nixpkgs calls these scripts during evaluation because “how limited the language is”. It’s literally just a script that does automated work for the package maintainers.

      • redw0rm@kerala.party
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        Probably that if possible, you can link to original article from itsfoss. And possibly for all such news ( unless its overly bloated / behind a paywall )

        • retiolus@lemmy.catOP
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          1 year ago

          I shared the article through my link precisely because the site is “overly bloated” with ads…

          screenshot

          If that’s a problem, no trouble, I’ll share the original links from now on!

  • Infiltrated_ad8271@kbin.social
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 year ago

    I find it hard to rate it positively, I see additional work and problems to solve things that have never been a problem for me. The last points are especially worthless with distrobox.

    • tony@lemmy.hoyle.me.uk
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      I’m the same… I setup a VM but it was so much work just to setup a basic machine with ssh I gave up on it… I’m also no sure moving all the config out of /etc into a script is scaleable at all. I get that by copying the script from one machine to another you can duplicate configs… but we already have ansible for that.

    • GustavoM@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      Indeed – why switching to a distro that tries to “reinvent the wheel”? Or even less so, one that makes (basic) things worse for the sake of “pros only”?

  • TDCN@feddit.dk
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I’ve been ripe for testing nix out for a while now, and I’m super excited. I just don’t have a machine to test it on first, and I absolutely hate dual booting. If I have energy one day maybe I’ll setup a VM to test it out in. I’m really hopeful to have it as my main daily driver os especially for its portability and stability.

    • jellyfish@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Nix is a great os to start in a container with. Because then you can come the mic files you developed there anywhere and have the same setup with one command

  • russjr08@outpost.zeuslink.net
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I find the concept of NixOS to be incredibly cool, and in terms of immutable operating systems it would in theory be one that I’m really interested in!

    But the last time I tried it, I found that I was constantly fighting the system, and the documentation is all over the place and confusing. There’s things like “Oh hey use Flakes!” but then most of the documentation doesn’t really cover Flakes because it’s still considered experimental, yet it feels like the majority of the community uses it.

    I also had software that would just randomly break, and when trying to track down the changes from Nixpkgs I couldn’t find anything that would prompt why it broke. Which… seems counterproductive to one of the strong points of Nix.

    One example I ran into, is OpenRazer - the service is no longer being exposed and was reported 7 months ago. I did my best to try to track down the changes that broke it, but I suspect it’s possibly a lower level change outside of the OpenRazer package/module that caused it to break.

    I get the impression that if I wanted to try to fix it, I’d have to take on the massive gauntlet of understanding how all of NixOS’ internals work, and while yes someday I’d love to have a better understanding, right now I’m more focused on just making sure the things I’d like (or even need in some cases, like software for my job) just works.