3 ms·

It hasn't changed! Except for PowerShell, but that's... oy. I have PowerShell, Git Shell and Cygwin running on my windows Dev box and all three make me cry on

It hasn't changed! Except for PowerShell, but that's... oy. I have PowerShell, Git Shell and Cygwin running on my windows Dev box and all three make me cry on a weekly basis because I have to switch between them to do different things. I suppose one day I will sit down to fix my Windows dev environment, but it makes me feel so bloody frustrated that my muscle-memory shell is so ... perverted by windows implementations. MS is bringing Bash to windows natively. I don't know how that is going to work since piping just isn't there, but I've got my fingers crossed that I'll only have to deal with ONE shell for windows!!!

meddlepal 6y ago
"Bash for Windows" is just WSL2 (forget WSL1 existed, as a proof of concept market validator it was good, but it has real issues because bridging NT -> Linux syscalls is hard.). It's not a native Bash experience but it's pretty close. I say "not native" because it's actually running a VM under the hood and bridging the file systems via 9P network protocol. I know people who are using it and love it. I have not switched yet, but I am definitely going to investigate it at some point.