You may find this interesting.
I know a of a few network and robot infrastructure startups that are actively looking at nix in their control planes. Many run linux already. If you can’t get Nixos directly running on them, then using nix as a build tool for them it probably a good start.
It’s a question of state. Ansible doesn’t really help you identify where state is, or if it’s needed, or how to manage it long term. Nixos cheats, by rebuilding the state of the machine from scratch via a declarative configuration rather than try to mutate state from the current system. It’s a very very nice cheat. It also has the weird side effect of making you learn about state, where it lives, and what you should be doing with it.
That’s not the fault of the Ansible it’s just how it functions. Nix is just another way of thinking about the system build and configuration task.
Nix solves a lot of these problems, but gives you some new problems, which are nicer to have.
If you are trying to ask if Ansible is better than Nix, then it’s an impossible question to answer, because they from not same school of thinking. Ansible just regurgitates what Cfengine does/did, where nix is a entirely new way of thinking.
It’s rather like comparing walking (or crawling) to traveling on Mr Musks Starship…
Both are involved in travel, one has been used for years and is the industry standard, but only one will get you to Mars.
If you want to go the Ansible route, then you won’t be without a job in a complex data center, deploying software to microsoft windows machines and cisco routers, however only time will tell if the job in the complex data center will make you happy.
ssshhhhhh…keep it quiet…Nix is pretty fun to work with…