Typing inside of the default WSL terminal feels amazing (2018)

Re:Typing inside of the default WSL terminal feels amazing (... by flowerlad on Monday December 23, 2019 @10:14AM (#21864061)

I was excited about WSL when I first heard about it. But that excitement quickly faded when I realized most real apps, such as gcc, don't work under it. The best way to get a Linux prompt on Windows is to use Docker. Use the -v option to share your drive.

[ Parent | on HN ]

Re:Typing inside of the default WSL terminal feels amazing (... by boston_sre87 on Monday December 23, 2019 @10:49AM (#21864346)

Think it'd be worth trying on wsl2 again. The first version was too slow to use, but I am loving wsl 2 now. The integration between windows and the wsl2 vm is a lot more seamless than it used to be. You can navigate the c drive from the wsl shell and also do stuff like `explorer.exe .` to open a windows folder app in the current wsl directory. The vscode integration is amazing as well. After using a mac for many years, it took me about a week to be sold on using a windows laptop from here on out.

[ Parent | on HN ]

Re:Typing inside of the default WSL terminal feels amazing (... by AndrewGaspar on Monday December 23, 2019 @12:13PM (#21865103)

I've never had a problem with GCC. GCC is, like, my primary use case.

[ Parent | on HN ]

Re:Typing inside of the default WSL terminal feels amazing (... by snazz on Monday December 23, 2019 @10:27AM (#21864165)

Most of those issues should be fixed with WSL2 given that it now uses a VM instead of syscall translation/emulation.

[ Parent | on HN ]