3 ms·
I've been on the WSL track for a while. I've found that when I live in a Ruby/Node/JVM/Clojure world, you'll run into all kinds of problems related to shelling
by augustl 9y ago
I've been on the WSL track for a while. I've found that when I live in a Ruby/Node/JVM/Clojure world, you'll run into all kinds of problems related to shelling out and handling paths that are bugs caused by all the developers and most of the community running on macOS or Linux. And I don't blame them, you can't test on all platforms, and all the languages seems to have APIs that allow these kinds of bugs to happen (representing a file system path using the fabulous data structure "string", for example).
I ended up selling my Surface Pro 4 after a year.
WSL is an amazing piece of tech, but due to the issues with windows compatibility of the software I use and run, I had to run it inside WSL. And since I use IntelliJ, that means the IDE has to run inside WSL, too. This worked fine, by running vcxsrv (an X server) from Windows. But then, after a windows reinstall, it suddenly stopped handling high DPI (retina) properly, and all the xorg apps where tiny. That's when I decided that I'm not gonna embrace a platform where I have to hack and slash to get the basics right.
I hope Microsoft works on bringing an official x server implementation to WSL. It's amazing tech, and I want to use it, but for now, it's too premature.