4 ms·
Just adding this in case anyone is using vs code and is wondering about dev on windows. I'd say that wsl is nice for some tasks but I wouldn't rely on it as a d
by nstart 7y ago
Just adding this in case anyone is using vs code and is wondering about dev on windows. I'd say that wsl is nice for some tasks but I wouldn't rely on it as a daily driver. It's great for installing some CLI tools to perform certain tasks. Maybe some file grepping or searching that you want to do with your local stuff but find it infuriating to do with powershell or bat scripts. This doesn't mean WSL is bad by any means. It's actually great. But not good enough. Not yet.
But I use windows as my daily driver and what does work amazingly well for me is virtualbox and running a VM as my developer machine on it. I run Ubuntu server. And for developing, VS code has this amazing feature that allows one to connect to a remote and develop on it as if it's a local filesystem. This includes having extensions that interact with the remote too. This also means I don't do the whole shared folders dance with all its oddities around speed and syncing anymore. Honestly, it changed the whole windows dev game for me.
Once the new terminal for windows is actually v1 (not holding breath for that. Theres a lot of work for that. Its probably going to miss the winter v1 projection) I think the windows dev experience will be complete.
- mixmastamyk 7y agoI’ve used sshfs for remote editing for a long time.