I'm very curious about this - as a mise user this seems like a redundant extra level of abstraction that I can't figure out the benefits of (& WSL definitely comes with at least some downsides).
From the OP I see:
> my long journey to keep my host installation free from all the changing and breaking dev dependencies that force a reinstall every few months
mise does this 100% for me (assuming we don't count mise itself as one of those dev dependencies). I'm struggling to think of what falls outside of it?
i agree. you can quickly import distro images into named WSL VMs (distros) to keep things separated. and you get close-to-native performance (especially by disabling kernel mitigations)
No need for mise just run separate wsl “distros” (VMs ) eg Debian-node , debian-Claude by importing root images . I use alpine because each one is tiny
I use mise inside WSL. It's sort of a terminal into "workspace" for me. Should probably spin an orbstsck or whatever to do thisnon my macbook
I'm very curious about this - as a mise user this seems like a redundant extra level of abstraction that I can't figure out the benefits of (& WSL definitely comes with at least some downsides).
From the OP I see:
> my long journey to keep my host installation free from all the changing and breaking dev dependencies that force a reinstall every few months
mise does this 100% for me (assuming we don't count mise itself as one of those dev dependencies). I'm struggling to think of what falls outside of it?
i agree. you can quickly import distro images into named WSL VMs (distros) to keep things separated. and you get close-to-native performance (especially by disabling kernel mitigations)
not sure I follow the context of this comment - did you mean to reply to me?
No need for mise just run separate wsl “distros” (VMs ) eg Debian-node , debian-Claude by importing root images . I use alpine because each one is tiny