bketelsen

I used my paper route money saved up for 2 or 3 months to buy a C80 when I was in 5th grade. I loved that thing so much. It was a fun moment of nostalgia clicking on this link.

Looks pretty good!

I hadn't seen this before, at first glance it looks interesting. I'll check it out, thanks!

the README is probably 50/50 hand written and LLM written. We haven't really done much to publicize the org yet, we were waiting for bootc to stabilize on Debian. Tomorrow is actually retirement day for the non-bootc installation paths so we may do some clean up in the future. Don't really have a burning need to become the next hot distro though. If atomic debian desktops and servers sound good we're here.

It really depends on how much of that other distro you really want/need. NSL's benefit for me is that it's headless unless I need a graphical app, then it shares the host's Wayland. My most common use case is an IDE inside a completely different distro from the host. If you want the whole desktop environment from your VM then NSL isn't your best route.

Hey one of the authors here. Surprised to see the submission. Happy to answer questions.

I'd love to hear your thoughts on it afterwards, either here or as an issue on GitHub.

... it's not. Just another way to keep my host clean and do the dirty work somewhere else. Where did reproducible builds come through? Another comment?

Most of these tools you mention are designed to work best as an overlay to your $HOME. toolbx, distrobox, and to some extent flatpak and snap. NSL is built to give you the "pet" virtual machines with limited integration to the host - you can get to the host filesystem if you want, and you can use the host's Wayland session. I think a better comparison would be using NSL instead of using a remote computer or VM.

Hi Brandon!

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.

challenge accepted!