> Most orchestration tools are stateless from run to run, and as such can't identify if a package has been removed. But NixOS is stateless from update to updat

> Most orchestration tools are stateless from run to run, and as such can't identify if a package has been removed. But NixOS is stateless from update to update as well. The key difference lies in the difference of scope between what is described in a playbook and what is described in a NixOS configuration file.