See this guide for using panes, which lets you split the window: To learn more about color schemes, visit

Mine sets a memory limit (see this post for more on constraining WSL’s resources) and enables host forwarding which means webservers run from WSL are available on Windows as localhost: Your WSL config is stored in the root of your user folder, for example /mnt/c/Users/scott/.wslconfig in WSL itself. Visual Studio Code, with the WSL extension, can treat WSL as a remote development environment just like any server or container. Personally, the only issues I’ve had using it have been related to the use of low-level devices, be they mapped devices such as serial devices, or abstracted devices like network devices. The second version of WSL is much more closely integrated with the host Windows operating system, being a full-blown Linux kernel running in Hyper-V (see this Microsoft article on the version differences). If you are on Windows, and do want to do technical stuff, then you can do worse than use the Windows Subsystem for Linux (WSL) together with Visual Studio Code and the Windows Terminal. I’m not going to start (and don’t want to have) the conversation about what desktop you should be on, but as someone who does as much with Office documents as they do with code I’ve been on Windows for some time. IntroductionĪs a bunch of techies, we’ve had plenty of those conversations about Macs vs Windows vs Linux. I’ve been using both the second version of the Windows Subsystem for Linux (WSL2), and the newish Windows Terminal for quite a while, and thought it’d be useful to collate some tips and tricks on them all into a single blog.

Windows terminal settings json location