Why not just install Powershell for linux?[1]

[1] : https://learn.microsoft.com/en-us/powershell/scripting/insta...

I could but no one else on my team (which is used to Linux) would touch my scripts.

It’s just too foreign for Linux devs whereas it ships with Windows.

Proprietary 'shell' vs. linux DIY/customized setup.

There are a multiple publically accessible/usable sources which can be found via search engine(s) to extend bash / unix shell functionality based on points discussed in topic link.

few article link topic snippits:

* approaches to autocompletion : [0][1]

* 'man' command and/or cli option -h to cli command shows 'docstring' / options

* jq resources for shell plugin[2]

--------------

[0] https://faun.pub/configure-bash-auto-completion-tab-completi...

[1] https://tiswww.case.edu/php/chet/readline/rltop.html

[2] https://github.com/fiatjaf/awesome-jq

Powershell is Open Source

https://github.com/PowerShell/PowerShell

that is a thing that started under Nadella's leadership, during the 90s it was a different story.

Those two "PowerShell"s are not the same. For the sake of cross platform deployment, they moved away from the original a lot -though they managed to support many things in time. The old and original one was released in 2006,IIRC, so it didn't exist in 90s.

Nowadays a lot of people script in python

> ... behaves differently on this computer...

vs. in linux, running powershell scripts under a virtualized instance of windows to avoid linux OS / windows OS differences issues?

----

other extreme end of the 'whitespace' spectrum:

APL : no white space / single character instead of multicharacter programming language tokens. Maximum expressiveness without any need for whitespace!

I put a note at the end about that: the lack of a `set -e` / fail fast equivalent was a dealbreaker for me.