• epyon22@programming.dev
    link
    fedilink
    arrow-up
    26
    ·
    1 year ago

    I came to the same conclusion. If I have a problem that I know nixos can solve it’s useful tool in my belt. But man you try to do anything out side the box the learning curve is massive. Good for those that know but when you only get to tinker a few times a week for a couple hours just getting things to work can be fun at first but gets old very quick.

    • 0_o7@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      2
      ·
      1 year ago

      Okay sure, but that’s like trying to use iOS and then saying it’s too restrictive. NixOS is pretty clear on what it offers and what it can do.

  • matejc@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    I read the article, this is not the first time that people think of Nix/NixOS like so. Its a standard case of wanting to use Nix ecosystem to the fullest, but you do not need to. You need to find the balance for yourself and that is different from person to person. I am using NixOs for about 9 years, and in whole that time I have never felt overwhelmed. People are just different.

  • NostraDavid@programming.dev
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    I don’t need reproducibility to the extent that NixOS provides

    Alright, that’s fair. As a programmer, I’ve been having a blast using it - being able to quickly setup my laptops almost the same as my desktop is such a breath of fresh air, then being able to copy over most of my config to a WSL setup to employ nix to get there 90% of the way on a Debian or Ubuntu WSL system is just so nice.

    But if you don’t need its features, or aren’t a programmer, I can very much imagine you’d rather stick to a more stateful system.

    • BatmanAoD@programming.dev
      link
      fedilink
      arrow-up
      18
      ·
      1 year ago

      If you drive a car, have you read the entire owner’s manual for every car you’ve owned? If you’re a homeowner, how about your hvac system? What about your system shell? Your compiler(s)?

      At some point you need your tools to be intuitive enough that you don’t need to read an entire manual in order to do your work.

      • TeamAssimilation@infosec.pub
        link
        fedilink
        arrow-up
        14
        ·
        1 year ago

        I suspect this attitude of “read the fucken manuel” comes from when tooling was simpler and you could actually read all the manuals (or buy a book) to learn every small bit of it. Today, I’d be surprised if someone actually read all the Windows, .Net, and Powershell docs before attempting to write a small script.

        Heck, even simpler things like Python have massive docs beneath every layer of them. You don’t learn everything from the ground up anymore, only the relevant parts to your use case.

    • bitcrafter@programming.dev
      link
      fedilink
      arrow-up
      16
      ·
      1 year ago

      I cannot speak on behalf of the article author, but as someone who personally is an imbecile, the answer is: definitely!