I have to say this is nice packaging. It is weirdly not obvious how nice it is to cleanly use a different “machine” inside your desktop.
I never thought I’d prefer WSL to even my MacBook for working with remote servers and dev but somehow I do.
I of course know the many ways to roll something like this for myself, yes dev containers are better for many things etc. but it’s wierd how good the ergonomics of a WSL like container are.
Thanks for saying so! That's exactly why I wrote this. The UX of wsl2 is just right. There are a lot of other ways to accomplish this, but none touch that same experience.
Have you tried mise? It handled most of that for me because dev environment is exactly what is needed per project
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