@zer0unplanned@friendica.rogueproject.org
Post #1080181
2026-03-27 11:42 UTC
@purrperl @thegardendude @codemonkeymike
NixOS doesn't require traditional scripting. Instead of writing imperative shell scripts to install packages or configure services, you define your entire system's desired state in a declarative configuration file using the Nix language.
This means you declare what your system should look like (e.g., "I want Firefox and a web server enabled"), and NixOS handles the "how" automatically. This approach provides powerful benefits like reproducibility, atomic upgrades, and easy rollbacks, replacing ad-hoc scripts with a single, version-controllable source of truth.
There is no other way..
Replies (1)
-
@purrperl@noc.social 2026-03-27 22:58
@zer0unplanned @thegardendude@regenerate.social @codemonkeymike@fosstodon.org I get the basic idea behind nixOS and its scripting language that handles configuration. I'm planning to replace the nix language with Ruby/Perl, since those languages are already known, and it would save people the trouble of learning the nix language, and would draw more people in to nixOS.