youwen5/liminalOS
1
0
Fork 0
mirror of https://github.com/youwen5/nixos.git synced 2024-11-24 17:53:51 -08:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Youwen Wu 2024-10-30 01:26:02 -07:00 committed by GitHub
parent 606536479f
commit 60999c4eb4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -14,7 +14,9 @@ you to build your own immutable operating system anyways.)
Many have written at length about the virtues of NixOS and _declarative Many have written at length about the virtues of NixOS and _declarative
configuration_ and _immutability_ and such. I doubt what I have to say is configuration_ and _immutability_ and such. I doubt what I have to say is
particularly novel, but I'll leave a few thoughts about Nix and NixOS and why particularly novel, but I'll leave a few thoughts about Nix and NixOS and why
they do things better anyways. Essentially: allow me to introduce you to the they do things better anyways. In particular, instead of immediately evangelizing about the virtues of Nix, I'll first motivate the reasons for why I chose a tool with exactly its properties, based on my use case (but not to worry, the evangelizing will come later).
Essentially: allow me to introduce you to the
origins of [NixOS God origins of [NixOS God
Complex](https://www.reddit.com/r/NixOS/comments/kauf1m/dealing_with_post_nixflake_god_complex/). Complex](https://www.reddit.com/r/NixOS/comments/kauf1m/dealing_with_post_nixflake_god_complex/).
@ -87,7 +89,7 @@ configuration, but don't install the software. But the software and the
configuration are fundamentally tied together; these are not concerns to be configuration are fundamentally tied together; these are not concerns to be
separated. If the software is installed, it almost always needs to be separated. If the software is installed, it almost always needs to be
configured anyways. If the configuration exists, the software should be configured anyways. If the configuration exists, the software should be
installed. installed. These solutions may work well for managing configuration, but they have the same issue as before: you also need to install the software you're configuring!
So, *nix hackers reach for things like [Ansible](https://www.ansible.com/), that So, *nix hackers reach for things like [Ansible](https://www.ansible.com/), that
promise automatic configuration of entire systems. Though Ansible was designed promise automatic configuration of entire systems. Though Ansible was designed
@ -100,7 +102,7 @@ which aren't expected to be as ephemeral as servers).
If you agree with the premises I've laid out up to this point, you might come If you agree with the premises I've laid out up to this point, you might come
to the conclusion that I've made: to solve this issue, we need a solution that to the conclusion that I've made: to solve this issue, we need a solution that
does _all of it_. A unified tool for deploying software and managing systems. does _all of it_. A unified tool for deploying software and managing systems.
And it must necessarily be declarative and reproducible. And it must necessarily be declarative and reproducible, because that is the only way to sanely manage a system. Imagine working on a programming project where recompiling with the same source code would non-deterministically produce different results based on the environment!
Well, [Nix](https://nixos.org/) is the _purely functional_ package manager Well, [Nix](https://nixos.org/) is the _purely functional_ package manager
(i.e. declarative, reproducible), and NixOS is a Linux distribution that is (i.e. declarative, reproducible), and NixOS is a Linux distribution that is