Re:Python support in Visual Studio 2017
by smcl on Thursday February 23, 2017 @03:06AM
(#13712410)
I can't speak for everyone, but for me a lot of the unix-y utilities and commands tend to do 99% of what I need with a couple of keystrokes and are very composable through piping/redirection. It's possible that equivalents exist on powershell but I feel like they're verbose and hard-to-remember or perhaps just plain different from what I'm used to working with for the last decade or so on OS X/Linux. For example if you need to access an environment variable like Path - on Bash you just use $PATH the same way you have forever. On powershell it's $Env:Path - maybe this makes more sense ("in the current execution environment, access the Path variable") but I had to google it to check and my first instinct was "oh it's something like %PATH% I think..." - which is the old windows cmd.exe way.
So maybe the biggest "pro" for the traditional linux command line way is "inertia" - but I'm sure someone else has a much more satisfying answer than mine
So maybe the biggest "pro" for the traditional linux command line way is "inertia" - but I'm sure someone else has a much more satisfying answer than mine