[giobox]

> The difference here is, your home directory is tightly integrated. This is something most (all) all virtualization solutions try to avoid.

This isn't really true - almost any virtualization or container solution will do this, in the case of containers it's typically just a local volume mapping. Of course the default is typically an isolated execution, that's one of the key tenets of containers or virtualization, but it's usually minimum effort to expose whatever local directory you like. I guess its nice this tool cuts out a small step to make the process convenient, but its not a must install for me personally vs my existing container runtime.

Mapping my entire home directory to a volume is a pretty rare use case for me too - i'm far more likely to just map a project directory to a working dir in the container. I don't think I have ever mapped my whole home folder to a container volume in my career, and can't imagine doing so in future either. This is a bunch of nice shell-scripting to do what you could already do with docker/podman a little quicker.

[dizhn]

> This is a bunch of nice shell-scripting to do what you could already do with docker/podman a little quicker.

This is absoulutely what it is. The project does not try to hide this fact nor am I.