I changed a mix of dockerkiles, shells, configs and others things to a SINGLE nix file. Is truly great. About complains: - Nix as "language": Is stupid, that

I changed a mix of dockerkiles, shells, configs and others things to a SINGLE nix file. Is truly great. About complains: - Nix as "language": Is stupid, that is true. As any other stupid language on this space, name it: bash (TERRIBLE), docker, yamls, pseudo-TOMLs, etc. So is not that worse than the median. I wanna know what other real option is here, except use a language as python instead. - Documentation: Is not lack of it, is how spread and badly stitcher together. is like docs made by JavaDoc. But I remember Docker at first, and I waste as much googling as with nix. Docker is not intuitive at all, and worse, it change per distro! The actual thing is easy, and the best thing is just look at the code. Most of it is not that hard to figure than docker files, yamls, etc. What was very confusing is the idea of how each config are done. Exist many things that are not "together" like setup NGINX also need to touch the firewall, then maybe systemd. Is not different to deal with unix, that is a mess, is that at first you think all is "just work" by default. More exactly: Not exist a clear convention that is applied everywhere. Lack of uniformity is the main trouble. Still, same as other tools in this space. Also: Very hard to debug things. Also 2: The hack around "home manager" to manage user config is a hack. Make not sense: I use too much time trying to do it "natively". Do it manually in *nix is so simple "just cat/touch this file in this path", so is the main reason I almost drop it. --- The whole migration for me take 1 week. That is not that much than before the first time I doit with custom docker files (One of the companies I work for before I use 2 weeks making it. This was when alpine/small containers were not as common as today). So, YMMV but the end-results is very nice.