I use Arch btw

      • ImgurRefugee114@reddthat.com
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago
        { lib, options, ... }:
        let
          names = lib.filter
            (name: lib.hasAttrByPath [ name "enable" ] options.gender)
            (lib.attrNames options.gender);
        in
        {
          config.gender = lib.genAttrs names (_: {
            enable = true;
          });
        }
        

        That way I know my configuration will always be comprehensive even when nixpkgs releases a new gender

    • Ignotum@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      Tried to switch, but a couple of pieces of software did not function correctly on nix, and i work a ton in python and i couldn’t get anything to work there, issues with missing system libraries and so on i think, i ran out of free time for tinkering and had to switch back

      I use arch btw

      • ImgurRefugee114@reddthat.com
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago

        It’s usually pretty straight forward to get python things to work once you know how, but yeah, you can still hit edgecases with poorly structured dependencies. Even in simple cases, having to package things as an end user can be a tough barrier. Personally, I find the pain to be well worth what nix offers me, but I know that it’s just not a good fit for the vast majority of people.

        • Clay_pidgin@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 months ago

          Is it? Every time nixpkgs changes the python minor version all of my virtualenvs break, which is a pain. I guess I need to look into dev shell or something.

          • ImgurRefugee114@reddthat.com
            link
            fedilink
            arrow-up
            1
            ·
            3 months ago

            Yes you need to use a shell to make it reproducible in the nix sense; a regular venv will try to point to the nix store or lose libraries (or try to dynamic-link stuff) when your system env changes which is why you need it to be independent of it.

            I don’t bother with venvs in my own projects because nix kind of subsumes its purpose, but it’s possible to work with them still.

            Something that might help: devenv. I haven’t used this personally but the UX looks like an upgrade. (I just use flakes with dev shells defined inline long-form)

            This video came across my feed last night, and might give you a rough idea: https://youtu.be/jldArhyi6jM&t=581

      • Martineski@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        Yeah, nixos btw is a big commitment that works only if you have enough time and/or you highly value what it provides. Though if you have lots of time to get past the learning curve and get things going the maintenance becomes much less of an issue later on which is nice.

        • Zozano@aussie.zone
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 months ago

          I’ve been using NixOS for the past 4 years.

          I started a business with the mission statement to replace local business machines with a windows-like platform, based on NixOS.

          I can say with confidence that the maintenance does not become much less of an issue, but it certainly becomes more transparent.

          • Martineski@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            0
            ·
            3 months ago

            Oof. Good to know. I’m lucky enough to only use it personally on a smaller scale where once something is set up I don’t need to touch it again and if I do it’s easy to do with the previously set up foundation. Do you regret using NixOS? Or do you think there are better alternatives in which case which ones?

            • Zozano@aussie.zone
              link
              fedilink
              English
              arrow-up
              0
              ·
              3 months ago

              NixOS is fucking GOATed lol. I can’t imagine a business managing a fleet which isn’t based on NixOS - what a fucking nightmare lol.

              How long have you been using it for? Because you will certainly run into complications eventually, as options change, packages become depreciated, and others get marked as unsafe.

              • Martineski@lemmy.dbzer0.com
                link
                fedilink
                English
                arrow-up
                0
                ·
                3 months ago

                Around half a year based off my commits which in retrospect is a short amount of time. It took me off guard because it felt like around a year before checking. Probably because of the steep learning curve that put me through a lot in a short amount of time. Lol

                I guess I will have my coming of age ceremony when I will bother doing my first major nixos update since I haven’t bothered doing one yet as I haven’t felt the need to warrant spending the time on it. ❄️

                • Zozano@aussie.zone
                  link
                  fedilink
                  English
                  arrow-up
                  0
                  ·
                  3 months ago

                  Oh lol. You’re not on unstable?

                  That explains why you’ve not had any issues lol.

                  Changing channels every six months is a dice roll - sometimes fine, other times shit breaks.

                  Depends how complex your system is I suppose, but the major releases are always the most work if youre pinning versions.