pellets VS nix-1p

Hello! A while back I made pellets as a way of keeping track what I installed on my system so that I could clean up things I didn't need anymore. It also made setting up a new machine much quicker. Really what I wanted was something like Nix, but I went on a very long saga trying to use it as a package manager with Arch and it was... not viable. So I made pellets as a middle-ground: it's just a simple bash wrapper around pacman and doesn't demand complete control, but you can use a configuration file to keep your packages synchronized to a desired state. It also prunes old dependencies. I've been using it for over a year now and am really happy with the result.

Fair enough. I've also had a couple of programs which weren't packaged already, fortunately it's quite easy to do so most of the time (or to just fall back to a distrobox container or flatpak in the worst case). If you decide to try it out, nix-1p and Nix Pills were great resources for me to get familiar with Nix and NixOS in a short time-span.

Wouldn't say there's a steep learning curve for the language itself, it's pretty easy to get a grasp around it imo. Here's a helpful page I used to quickly get familiar with the language: https://github.com/tazjin/nix-1p

What's rather messy about Nix is nixpkgs with its helper functions all over the place alongside pretty shallow / non-existent documentation (which is unrelated to the language). Thankfully they've started to work on that recently: https://discourse.nixos.org/t/documentation-team-flattening-...

I wrote a language tutorial for only the language a while back, and have gotten the feedback that it has helped a lot of people - maybe it'd clear something up for you: https://github.com/tazjin/nix-1p

For Nix language things I really like this page: https://github.com/tazjin/nix-1p