He did note that in the article. It's under 1). at the bottom as well.
> "I realize PowerShell is cross-platform (I wrote this on macOS) but good luck evangelizing it to teams used to Linux."
Well, this is about his _own_ use no? So why not just use powershell in Linux? If it's good, tell us why. I actually am in the same boat. I spent a lot of time learning it, and I do know bash, but not as well. If there is a happy medium here, it's nice to hear your experience about that. Not just say 'well good luck convincing others'.
greatgib · 1h ago
I think that it is just the case of a Windows power user that is so used too it's ecosystem that he did not yet aquire the ease of use of linux native things.
PowerShell give the impression of being simple for basic users but it's a cluster shell of complexity. With a mess of everything being subtly different and broken. Just look at the case of Microsoft that hijacked the curl command in PowerShell with different arguments.
It's even worse if you are an intense user of vscode because they will obviously go hand to hand.
The whole article has proof of my opinion.
For example:
still have not bothered to add tab completion to my shell scripts because of the extra steps involved. I am lazy.
PowerShell gives you this for free when you write a “cmdlet”
He says that PowerShell gives the completion for free but for that he has to create a cmdlet and fill the prototype and typing info going with it.
And that will just give you basic argument completion but not logical one like a lot of tools do.
So it is not at all "free", just it is used to do it with PowerShell so doesn't notice the cost anymore. Like people saying that they never encounter bugs and annoying issues with Windows when they have some every few hours but they are totally used to it anymore.
account-5 · 5h ago
What about Nushell? It's still a separate install on all platforms, and not POSIX compliant (for reasons). But for me it's got all the benefits of powershell without the verboseness and imo a less obscure data structure.
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.
rastignack · 2h ago
Nowadays a lot of people script in python
sargstuff · 11h ago
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.
> "I realize PowerShell is cross-platform (I wrote this on macOS) but good luck evangelizing it to teams used to Linux."
Well, this is about his _own_ use no? So why not just use powershell in Linux? If it's good, tell us why. I actually am in the same boat. I spent a lot of time learning it, and I do know bash, but not as well. If there is a happy medium here, it's nice to hear your experience about that. Not just say 'well good luck convincing others'.
PowerShell give the impression of being simple for basic users but it's a cluster shell of complexity. With a mess of everything being subtly different and broken. Just look at the case of Microsoft that hijacked the curl command in PowerShell with different arguments.
It's even worse if you are an intense user of vscode because they will obviously go hand to hand.
The whole article has proof of my opinion.
For example: still have not bothered to add tab completion to my shell scripts because of the extra steps involved. I am lazy.
He says that PowerShell gives the completion for free but for that he has to create a cmdlet and fill the prototype and typing info going with it. And that will just give you basic argument completion but not logical one like a lot of tools do.So it is not at all "free", just it is used to do it with PowerShell so doesn't notice the cost anymore. Like people saying that they never encounter bugs and annoying issues with Windows when they have some every few hours but they are totally used to it anymore.
https://www.nushell.sh/
[1] : https://learn.microsoft.com/en-us/powershell/scripting/insta...
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...
[1] https://tiswww.case.edu/php/chet/readline/rltop.html
[2] https://github.com/fiatjaf/awesome-jq
https://github.com/PowerShell/PowerShell