NixOS breaks. All. the. time.
It does that when you're starting out.
Error messages are cryptic
Programming is like that. Learn how to use the repl.
With less snark this is an interesting concept (word??).
But nix is a programming language, not an ini file (like aconfmgr).
Huge update sizes
No argument there.
Compilation takes forever (and binary caches are unreliable)
Wait a week. (I think they are referring to flakes/dependency pinning, honestly another interesting problem.)
Poor documentation
Read the source. (Sometimes this is a cop out. (sorry) Sometimes it is the only way. I was thinking personally about auto-generating source - DeepWiki is a great introduction to what is possible on this front, yet it would seem that a couple more rounds of iteration and feedback/competition is necessary before documentation writer are not actually necessary anymore.)
aconfmgr is "declarative"
aconfmgr is written in bash for arch.
dcli is written in rust for debian.
there is another one as well written for arch.
declarative and immutable and reproducable: i guess people need to get used to the new words.
system-manager
This would be a god-send (ill revise with a different word) if I had read (and understood) all the nix code it seems like I'm claiming I did.
As it stands, I'm still getting used to blueprint, which is a great first issue for somebody wanting to customize calamares. (aka note to self)
--- more draft notes
Some guy wrote an interesting post about his journey with nixos. I think that these pieces, scattered amongst the webs are interesting and valuable, and here I will attempt to do a more serious "reaction" to it, and then go to bed.
One note before I begin is that it is nice to see more well reasoned and well thought out things, especially on topics that some of the younger (international?) generation might not have the interest or exposure to.
Top comments (0)