| > Very few use Powershell for Linux because it doesn't pre-installed on a Linux box I don't buy that. On a GNU/Linux box, there's few things that are easier than installing a new shell, if you prefer a different shell than bash it's two commands away. Bash does the job people expect it to do and would probably be _very_ alienated it they'd had to start messing around with .net gubbins. >And yes I would prefer your second "mental overhead" way as it involves less typing Maybe for the first time you would. Maybe if you were to accomplish this specific thing. Anything else? Have fun diving into the manpage of your shell _and_ the programs you want to use, and you better hope they share a somewhat common approach to the implemented (object) datatype or well, good luck trying to get them to talk with each other >Powershell is unfortunately not the shining example of a shell that best leverages structured/typed input/output succinctly I would just remove the last part, then agree with you: ">Powershell is unfortunately not the shining example of a shell" > Nearly every IT department that manages windows machines uses Powershell I mean, what other choice do they have there? cmd? Yeah right, if you want to loose your will to live go for it |
When you are SSH'ing into one of 10k containers for a few commands, you will only use what is already there. Bash is there and works and that is what one will use 100% of the time. No one is going to permit Powershell to be bundled to satisfy personal preferences.