3 ms·
It’s fascinating, really, that Microsoft has narrowed the gap so rapidly with WSL. I read these steps–which I performed for years over the space of a few machin
by owenwil 7y ago
It’s fascinating, really, that Microsoft has narrowed the gap so rapidly with WSL. I read these steps–which I performed for years over the space of a few machines–and am amazed at how janky the tooling is. WSL/WSL2 are clearly pushing to build better ways to create developer tool chains, without all of the janky macOS specific stuff. With everything being a container, and inherently disposable, along with all the investment Microsoft is making into VSCode and its remote tool chain, it’s a good time to be a dev on Windows (and I genuinely didn’t think I said that when I switched two years ago).
- giancarlostoro 7y agoI am not an expert by any means but isnt Docker just good enough for this case as well? The benefit of WSL is that it doesnt consume more memory than it needs to has been my experience. I am not entirely sure of the memory consumption of Docker.
- AlexeyBrin 7y agoDocker on Windows runs in a VM through Hyper-V, by default it allocates 2GB of RAM per container (you can change the defaults if necessary).
- owenwil 7y agoDocker is nowhere near as close to the metal as what Microsoft has done with WSL2—it's got better performance and runs as near-native as you could possibly get.