1. You have to create a separate volume just to install a package manager, which is a poor user experience
2. A separate volume means FileVault won't work out of the box
3. The volume can be mounted only after GUI apps are brought up
4. Restoring after sleep might fail because of 3
All of these are mentioned in the Github issue, but it might be hard to find because it requires so many clicks and scrolling to view the whole thread.
2 — Could you explain? Mine is on and working, I didn't need to do anything else.
3 — Is this if you have login items that need nix to be available? I don't have this so I haven't noticed.
4 — I've never run into this, but again I might just not use Nix for the kind of things that would cause issues.
1. Having to create a volume when a plain old directory should suffice is insane. It's creating a hassle for no good reason for users.
2. /nix would be unencrypted by default if kept in a separate volume. There's also the problem of how to unlock it upon boot.
3. Login items is a very common use case so not supporting it would be problematic for many users.
4. Unreliable sleep is an even bigger problem.