Learn a dynamic lazy functional programming language first and then start building a flake without much help or documentation because that’s what you should be doing and the default installation doesn’t use that mechanism. The docs you find will assume you understand category theory already.
About few years later you are a god and there is no way you’re going to use anything else ever again.
He didn’t explain it well. The whole system lives on a ymal file and is easy to read. Documentation as code. If you have a working system then you’re set, it’ll never break. Adding software uses it’s own dependencies and will never break other software. It also has roll back features like snapshot/btrfs, during bootup you can go back to a previous version of your system. With the ymal file it makes it easy to clone the setup from others or for other systems of yours in the future, just have to generate a hardware file in most cases.
Learn a dynamic lazy functional programming language first and then start building a flake without much help or documentation because that’s what you should be doing and the default installation doesn’t use that mechanism. The docs you find will assume you understand category theory already.
About few years later you are a god and there is no way you’re going to use anything else ever again.
Source: been a user for the past four years.
I understood maybe three things in your reply so NixOS probably not for me.
He didn’t explain it well. The whole system lives on a ymal file and is easy to read. Documentation as code. If you have a working system then you’re set, it’ll never break. Adding software uses it’s own dependencies and will never break other software. It also has roll back features like snapshot/btrfs, during bootup you can go back to a previous version of your system. With the ymal file it makes it easy to clone the setup from others or for other systems of yours in the future, just have to generate a hardware file in most cases.