Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not pointless if you are working on a windows project but using unix tools to search code, do commits, etc. WSL2 just isn't usable for it in large projects. git status can take 5 minutes on unreal engine.


If you just need the stock Unix command line tools, MSYS2 will give you them at native speed, no VM needed, no funky path mappings etc.

WSL is for when you actually need it to be Linux.


I don't need just stock commandline tools, I use Claude Code etc. Maybe it can work in msys2 (it uses node) but it works well in WSL1. Also do a good bit with Python where some dependencies haven't worked in msys2.

I do windows and android gamedev and the server side is Linux.

However, WSL1 is pretty much abandoned and lots of newer distros have moved to forcing systemd or container based stuff that doesn't work in it, and some elf binaries no longer work in it (including newer node.js versions).

I use WSL2 as well when I really need it to be Linux and am doing webdev or something.

I use msys2 for a few things, usually compiling windows dependencies with the gnu toolchain that need GCC's stuff like inline assembly or computed goto (codecs etc.). Maybe possible from wsl1 too but they usually have full build and dependency instructions for msys2.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: