Hacker News new | ask | show | jobs
by frenchyatwork 2086 days ago
That's really over-selling it. WSL is okay. It's better than the previous monstrosities, but that's not saying much. You can't run VS Code in WSL, it literally has code to prevent you from doing that, even if you have a functioning X Server (which is a jolly pain to set up).
2 comments
filmgirlcw 2086 days ago
(Disclosure: I work at Microsoft but not on WSL2. I’m just a huge fan and I say that as a dedicated/devout Mac user)

Two things:

First, GUI support is coming [1] and the team is working to support both X11 and Wayland [2].

Second, the Remote Development Extension for VS Code [3] lets you do this seamlessly. It auto-configs to work with WSL or WSL2 and can also connect to a container or remote machine or GitHub Codespaces codespace. It’s awesome and all of your files, your terminal, everything is mapped to WSL2, with all the GUI parts from Windows. It’s one of my favorite things.

I’m not trying to convince people that WSL2 is the end-all be-all, even though I’m an unabashed fan, but I just want to correct the record a bit (regarding VS Code) and share that X11/Wayland GUI support is coming

[1]: https://devblogs.microsoft.com/commandline/whats-new-in-the-... [2]: https://youtu.be/b2mnbyRgXkY [3]: https://code.visualstudio.com/docs/remote/remote-overview

link
Bedon292 2086 days ago
Why do you want to run VSCode from inside WSL?

The Windows version can be fully integrated with WSL. Windows handles the GUI, Linux handles the CLI and all that. [1]

I have not found any need that it does not meet this way, but as I mentioned in another comment, I have a very narrow focus. So would not be surprised if I was missing something.

[1] https://marketplace.visualstudio.com/items?itemName=ms-vscod...

link