I agree, new devs should learn linux. If you're on Windows, WSL2 is the way to go. This has been a game changer for me. Fortunately, my journey into servers also happened the same time WSL was getting better. WSL2 is awesome - especially if you use docker. I actually tell some up & coming developers who use windows to start developing strictly in WSL2. So it becomes their "developer" world/environment. This builds confidence working in a command line, so when they're asked to get into a container or a dev server, they aren't shy about it. I use Ubuntu with WSL2 - seems to have the best compatibility with docker from experience. Also very excited for the ability to add a GUI for WSL2.
I also do graphics work and game on my windows 10 machine. Windows 10 is now a great (combination with WSL2) for development.
oh really? I don't really pay attention to time in there. I know there were some serious issues before, networking for example, but updates took care of that. wsl2 works well for what I use it - VS code remote and docker (docker compose not k8s). I do mainly php, Node.js work
I agree, new devs should learn linux. If you're on Windows, WSL2 is the way to go. This has been a game changer for me. Fortunately, my journey into servers also happened the same time WSL was getting better. WSL2 is awesome - especially if you use docker. I actually tell some up & coming developers who use windows to start developing strictly in WSL2. So it becomes their "developer" world/environment. This builds confidence working in a command line, so when they're asked to get into a container or a dev server, they aren't shy about it. I use Ubuntu with WSL2 - seems to have the best compatibility with docker from experience. Also very excited for the ability to add a GUI for WSL2.
I also do graphics work and game on my windows 10 machine. Windows 10 is now a great (combination with WSL2) for development.
👍👍
WSL, even with 2, is quite a broken hack. A lot of things simply do not work correct. One enormous issue is time, it is almost constantly wrong.
oh really? I don't really pay attention to time in there. I know there were some serious issues before, networking for example, but updates took care of that. wsl2 works well for what I use it - VS code remote and docker (docker compose not k8s). I do mainly php, Node.js work
In WSL2 there is also a memory issue due to normal Linux kernel behavior of disk caching. This will cause VM to eat into your normal memory.
See github.com/microsoft/WSL/issues/4166
whoa. and the issues is still open 😅.
thanks! I'll keep an eye out for that. currently seeing only 250mbs of memory being used by it.