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.
It’s just too foreign for Linux devs whereas it ships with Windows.
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...
During scripting they can be constantly annoyed by Python's indentation errors. Really awesome stuff when your syntax is whitespace dependent.
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!