Re: ksh or nothing, thank heavens for cygwin
"The idea that passing unstructured text around is the best solution for anything is just bizarre."
Not really. Well, really really not really for Windows CMD.exe. Let me explain...
We all know BASH can't handle binary data due to how Unix/C handles null. However, there is all kinds of tools available to BASH to take care of that processing. With Windows CMD, these tools are extremely limited or they just do not exist. Honestly, besides copy /b, what else does CMD have available to it for binary data?
Objects aside, even the simplest things in BASH are extremely cumbersome in Windows CMD. For instance, null terminated lines! In BASH you'll just use a tool like 'find' and have all lines null terminated. In Windows CMD, good luck!
Is Powershell a upgrade to CMD.exe? Absolutely. Is Powershell the best alternative? No, I think it never has been. Truthfully in my opinion, with so many shells and languages today that are better than Powershell, I can't help to think that advertising CMD's replacement with Powershell as a struggling effort to win BACK people who have already have been accustomed to many OS's that are not Windows.
First things I have done returning to Windows for _SOLELY_ running Photoshop...
1. Enable Hyper V
2. Install Docker
3. Forgetting Windows for anything other than Photoshop.
P.S. If anyone knows how to run 10-bit color for usage in Photoshop that does NOT require running Windows as the host OS, please, please let me know! I've tried all the popular VM's and other virtualizers out there without luck. Being I'm not a "VM" guy, I'm hoping there is a way to NOT virtualize GPU hardware but still virtualize everything else...or something...anything.