In this article I share my learnings on remotely accessing your Windows 10 computer. My motivation was to determine efficient ways to access both the Windows environment, and the WSL2 development environment from another computer.
I’ve long used macOS or Linux when I make my Open Source contributions, but I think that the time is right to try Windows as a full-time development environment. If you want to jump on board, this article series is for you!
It all started with a simple tweet from @nunixtech:
Lately I’ve been on a mission to separate my development environments by project, and by category (personal/work/Gophercon/etc). The writeup on the Gopheracademy blog describes a fun way to create an isolated container-based environment for each project by using LXD on Ubuntu.
I want to document a setup that I’ve found that works really well for me using Windows 10 and Windows Subsystem for Linux for general development. Before we dive into any specifics, though, I want to provide some background and explain my objectives which will help to frame the decisions I’ve made and the trade-offs chosen to reach a more ideal environment.
TLDR; I’ve traded in my Mac on a Surface Pro. Here’s why:
That might be the longest title for a blog post ever, but it’s kind of hard to describe what’s going on here if you’re not familiar with the latest updates from Microsoft land.