Comment

Comment by abrookins

Actually, it was as recently as this very week! Running with all the latest updates on a new Surface Book 2, I ran into a variation of this open issue: https://github.com/Microsoft/WSL/issues/1982.

That was only the last and final blocking issue I ran into, after a series of minor (or at least, not serious) problems that I powered through during too many late nights.

Couple of things:

- Hyper-V. Was excited for this and tried it, since I had already set up Docker for Windows and pointed the CLI tools in WSL at it. However, Hyper-V didn't appear to have any support for the "shared folder" concept that VMWare and VirtualBox do. Is your only option here to set up Windows share and use Samba?

- I dislike running VMs generally, but would have gone that route if I could have gotten a setup I liked. However, after reconfiguring everything to use VirtualBox (including Docker) and creating a single VM there to do Docker and Linux stuff on, it seemed to tax the machine too much (i5 8GB SB2). With a beefy machine that would have worked better, but Windows 10 isn't that appealing if I have to buy the highest-spec machines and run VMs... that's exactly where it was 5-10 years ago.

I have a lot more to say about WSL and Windows 10, and it probably deserves a blog post. I haven't returned the Surface yet because I'm kinda in love with it, but also if I can't do all my work on it, then it's not something I need to own.

parent abrookins 8 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton