3 ms·
I don't use windows but in your case it solves this problem better with wsl2 since you can have the same real linux that runs on your servers.
by Scarbutt 6y ago
I don't use windows but in your case it solves this problem better with wsl2 since you can have the same real linux that runs on your servers.
- thekyle 6y agoI really wanted to like WSL 2 but it has a lot of bugs that may take years to get ironed out (unusably slow disk IO, memory leaks, virtual disks that grow forever, etc.) I think it would probably work for web development as long as you keep everything inside WSL, but for other development tasks you're going to run into issues real quick. https://github.com/microsoft/WSL/issues/873 https://github.com/microsoft/WSL/issues/873 https://github.com/microsoft/WSL/issues/4197 https://github.com/microsoft/WSL/issues/4197 https://github.com/microsoft/WSL/issues/4166 https://github.com/microsoft/WSL/issues/4166 https://github.com/microsoft/WSL/issues/4699 https://github.com/microsoft/WSL/issues/4699
- Cu3PO42 6y agoAnecdotally I've been doing development in C++, Rust, .NET and other languages just fine in WSL2.
- nickjj 6y agoI use WSL 2 for full time development on the stable release of Windows 10. The last 2 issues are an issue as of today but you can workaround them where it becomes a non-issue in the end by setting 1 config file value and running 1 command maybe once a month. Also if you keep your source code inside WSL 2's file system then the first 2 issues are non-issues in practice.