> I'm curious what cli tool you find is better on linux?
It's not so much individual tools being better, but rather the whole unix shell ecosystem is still very much the dev default that everything command-related 'just works' from linux shells. Kind of the opposite from the GUI situation.
WSL2 doesn't lock you out of the windows filesystem, it just slows it down. I found when working in Windows I preferred keeping everything in the WSL2 image, for speed & simplicity (no messing about with wslpath!). So to that extent I agree with your 'fighting Windows' comment.
I don't want to exaggerate the differences - everything works in both, particularly in an age where developer toolchains are becoming ever more platform neutral (node, go, rust, java etc).
It's not so much individual tools being better, but rather the whole unix shell ecosystem is still very much the dev default that everything command-related 'just works' from linux shells. Kind of the opposite from the GUI situation.
WSL2 doesn't lock you out of the windows filesystem, it just slows it down. I found when working in Windows I preferred keeping everything in the WSL2 image, for speed & simplicity (no messing about with wslpath!). So to that extent I agree with your 'fighting Windows' comment.
I don't want to exaggerate the differences - everything works in both, particularly in an age where developer toolchains are becoming ever more platform neutral (node, go, rust, java etc).