Personally I haven’t. While Linux is imperfect, choosing the right distro makes the rest of the experience straightforward. And with it’s whole complexity, I find Linux more user friendly than Windows. Even driver issues, broken shadow file ownership and KDE specifics only made me more confident about my choice to use Linux after I solved everything.


And changes will last on reboot, y’know with the whole immutable thing?
EDIT: I couldn’t find straightforward (to me) info on this even searching for stuff like ‘NixOS mutable home’, but after the reply to this I tried different terms and found the wiki page on impermanence. Specifically, the persisting+home managing sections:
and
Absolutely! I’ll give you an example. In the NixOS config for my desktop I have the lines:
{ environment.systemPackages = with pkgs; [ firefox ... ]; }So Firefox is installed every time I build a system with this config. This is just like
apt-get install firefoxin that very user can use it after installation. The config lives in the respective user’s dotfiles (.config/mozilla/firefox) and will of course survive reboots.What I chose to do additionally (but this is in no way required!) is a
home-managerconfig for my main account with the lines:{ programs.firefox = { enable = true; policies = { DisableFirefoxAccounts = true; DisablePocket = true; DisableTelemetry = true; DownloadDirectory = "${config.home.homeDirectory}/tmp"; OfferToSaveLogins = false; ... } ... }This is a declarative configuration that basically handles my dotfiles (profiles, extensions, themes, …) for me. I think you have the impression that this is mandatory, but it is really a very specific behavior through the home-manager module, but you can absolutely run NixOS without it.