101–106 of 106 posts
I post this on every post about Nix I encounter, but I sincerely hope that it gets static electricity typing one day. I have yet to try typenix (a fork of the typescript compiler applying the typescript type system to nix) https://github.com/ryanrasti/typenix
> static electricity typing I assume that was an autocomplete typo?
I would love a Bazzite-style nixos distribution. Like batteries-included for gaming. Is this kind of thing common in the NixOS space ? Like configs you can import that manage 99% of the os for you ?
Not the same thing but you can go in the other direction using https://blue-build.org/reference/recipe/ . You can have a nixos-style bazzite distribution where you import the bazzite base image and layer your custom config on top of it.
After using NixOS for a bit and eventually learning to rely on it, life without it seems inconceivably complex
I love the slightly weird learning curve on NixOS where initially it seems incredibly complex writing this weird functional programming language for every change you want to apply to your system, then over time it clicks and you end up in a place where any operating system that doesn't define everything in a weird functional programming language seems incredibly complex. I read blog posts about doing things on other…
I had quite a rollercoaster going from Windows 10 to Arch to Windows and then settling on NixOS. Main reason being able to do clean package/program setup and centralize, version-control my configuration. My main issue with Arch was that after installing and trying stuff it left OS dirty even after package removal. This might be because I had some things built and installed through AUR (e.g. latest mpv releases that s…
> My main issue with Arch was that after installing and trying stuff it left OS dirty even after package removal Yeah, that's literally a problem with every single OS that is not NixOS (or, shoutout, Guix, or the other Nix-based variants). That's also why I am sticking with NixOS. Been at least 5 years now- it's wonderful having a reliable LINUX system as my daily driver (or one of them). And you can reboot into any…
Earlier quoted context omitted.
> My main issue with Arch was that after installing and trying stuff it left OS dirty even after package removal Yeah, that's literally a problem with every single OS that is not NixOS (or, shoutout, Guix, or the other Nix-based variants). That's also why I am sticking with NixOS. Been at least 5 years now- it's wonderful having a reliable LINUX system as my daily driver (or one of them). And you can reboot into any…
Not a Nix user yet, so i'm wondering if you can describe a little more about the "reproducibility" aspect which implies that you are often "reproducing" stuff. What needs reproducing? What is a basic daily-driver use case for whatever we are "reproducing"?
The builds are deterministic, unlike on any other linux or other OS, because Nix basically captures a closure of all the possible inputs to a build, which means that the build always "sees" the same things, which means it always builds the same way. Once you grok this, doing it any other way will seem insane.
Truth be told I think I only appreciated it more after having used (and bricked) other Linux distros simply by "installing the wrong thing". This is what i mean by "daily driver". You need something reliable AND reconfigurable for that; NixOS (or nix-darwin on Mac) offers both.