|
>Dockerfiles are much simpler than nix configuration I highly doubt this, Dockerfiles are simpler for a hello world microservice, but they get worse and unmaintainable when you add them lots of them with docker-compose. >ostree is the future, not nix
>flatpak takes care of the desktop aspect I really hate the approach this approach, it just moves the state from the root system to the user. The root directory is immutable, but you move the whole responsability to Flatpak, which is not even comparable to nix.
Meanwhile, in case of Nix, the whole system is reproducible and settings are more and less immutable. >it's too complex My whole nix config (with specific configs for vscode, neovim, chromium, wireguard, rust, python, nodejs, c++, go) is less than 600 lines of code, and it's readable. Also I configure most of my open source projects via nix as well as it's pretty easy to share the environment with the other developers.
Nix works everywhere, on every linux distro, macOS and even Windows via cygwin or wsl. >under documented That's a really good point, nix maintainers didn't care much about documentation, but usability. But it looks like that's changing, they moved docs to mdbook and a team is working specifically on improving the docs |