The amount of work it takes to migrate #NixOS to a new device is just too much! 😁
@eliasp While I know what you mean, I strongly disagree with that truncation.
First, the nixos hardware module needs to exist & support all of your particular hardware. This isn't a given thing depending on the HW you are about to use.
Secondly, there are still too many settings you need to do manually such as xfce environments, lots of app settings, ...
I started with NixOS in the naïve assumption that it is allowing me to define everything across all of my computers. I failed miserably & with the next opportunity, I'll switch back to Debian.
However, if you're totally open to let the #NixOS community to choose the hardware platform (devices that do have a HW config module which supports all features), desktop environment (sway?) and all apps for you, then you're probably fine with "everything in your #Nix configuration". If not, you do spread misleading vibes here - so to say.
And yes, there's still the issue with not being to run #Python in a normal way.
HTH
@publicvoit I'm an ex NixOS user, and I'm using GuixOS now. Migrating a working setup to another system is usually a joy in #NixOS and #GuixOS. Also studying the setup of others, and copy and paste good idea. But I agree that creating this "magic" working setup can sometime be a pain.
Moreover, if an application is also a platform, supporting plugins like Emacs, KDE, or IDE like Jetbrains, then it cannot work correctly in a Nix/Guix OS environment, because it is not running in a Filesystem-Hierarchy-Standard, and ideally also the plugins should be ported to Nix/Guix.
Summing up: what works, works very well, since it's reproducible and all in a few files (as reported by @eliasp ), but what doesn't work can be very difficult to port to Nix/Guix (as reported by @publicvoit).
