3 ms·
Depends if you care about doing anything natively on Windows or not. Say Windows has perfectly good native support for NodeJS. If you go with WSL you'll be runn
by auganov 6y ago
Depends if you care about doing anything natively on Windows or not. Say Windows has perfectly good native support for NodeJS. If you go with WSL you'll be running WSL's Node. Many may not want that.
Java/Clojure same deal. There's no problem with them on Windows. Running everything under WSL sounds like a big compromise to make to me. Though for Java/Clojure I could imagine you could still for most projects start your software from the normal java.exe as jars generally don't have platform specific code. But in my codebase I do actually use a few libraries that are system specific.
- tjoff 6y agoYou can run windows apps within WSL too though. (I guess maybe not WSL2)
- auganov 6y agoWell the thing is if you npm install a lot of stuff using the WSL version there may be packages that include platform specific stuff. Then trying to run it with the native node might not work. But thinking of it I guess you could have all the WSL scripts use the native version. Not sure if there would be issues. Or let's say you have to compile something that you want to use as a child process in your software. If you compile that under WSL (correct me if I'm wrong[0]) it's not going to be easily accessible to normal Windows apps. [0] I see that now there's some way to invoke wsl commands from regular Windows but not sure how that works exactly.