When your read reviews of Linux distros, a lot of the time you will hear the terms, “Rolling release” and “Point release” a lot. A point release distro has many different versions, while a rolling release distro has one version, that gets continually updated, and you will never have to upgrade to a new release. Having a rolling release distro or a point release distro is one of the most important decisions when it comes to what Linux distro you want to use, so I am going to explain why you should consider using a rolling release or point release distro.
i’ve tried nix three different times and find the learning curve so incredibly steep that the productivity gains are simply not worth it for my desktop usage. i’m waiting for the space to mature so i can feel better about picking it up.
Totally understandable. One day we may see a graphical installer and configuration manager and that is the day I can start recommending others to try it
the installation process is actually alright, it’s moreso the maintenance that i had problems with. the mental model is still foreign to me and when i tried it last flakes were recommended by most forum users but not in the documentation. almost all public repo’s made use of flakes and it just confused me :/
The most confusing part of flakes is that it isn’t the default, but sort of defacto is because so many use it (myself included). At this point I feel it should be the default. The installation process doesn’t use the flakes feature so it has to be worked around and it isn’t straight forward.
Nix(OS) has a case of expert user base that aren’t motivated enough to make it easier for those unfamiliar with the concepts to get going.
Nix makes more sense if you understand referential transparency and functional programming. Even then, how a lot of nix expressions are written is quite confusing with all the self-recursive overrides, functions that are somehow also sets etc.
The best documentation and tutorials are probably somewhere other than in the official ones (though official documentation is not bad). Nix Pills and the wiki, especially.
i’ve tried nix three different times and find the learning curve so incredibly steep that the productivity gains are simply not worth it for my desktop usage. i’m waiting for the space to mature so i can feel better about picking it up.
Totally understandable. One day we may see a graphical installer and configuration manager and that is the day I can start recommending others to try it
the installation process is actually alright, it’s moreso the maintenance that i had problems with. the mental model is still foreign to me and when i tried it last flakes were recommended by most forum users but not in the documentation. almost all public repo’s made use of flakes and it just confused me :/
The most confusing part of flakes is that it isn’t the default, but sort of defacto is because so many use it (myself included). At this point I feel it should be the default. The installation process doesn’t use the flakes feature so it has to be worked around and it isn’t straight forward.
Nix(OS) has a case of expert user base that aren’t motivated enough to make it easier for those unfamiliar with the concepts to get going.
Nix makes more sense if you understand referential transparency and functional programming. Even then, how a lot of nix expressions are written is quite confusing with all the self-recursive overrides, functions that are somehow also sets etc.
The best documentation and tutorials are probably somewhere other than in the official ones (though official documentation is not bad). Nix Pills and the wiki, especially.
i’ll be referencing these next time i want to try it out again. thanks!!