5 ms·

I love PowerShell. I've built CLI apps, desktop GUI apps, web apps, and integrations using it. Now that I can use it on Mac, Windows and Linux it's even more va

I love PowerShell. I've built CLI apps, desktop GUI apps, web apps, and integrations using it. Now that I can use it on Mac, Windows and Linux it's even more valuable to me. It isn't without a few shortcomings, but I've tried picking up other languages and keep returning to what makes me productive and happy: PowerShell. I've read the criticisms, and experienced some of them firsthand, but considering all that I've been able to do with PowerShell the good far outweighs the bad.

mxuribe 4y ago
I'm curious....are the shortcomings that you encounter the types where elements of your scripts need to differe between Mac, windows, and Linux? I ask because i really don't like powershell...but am crafting more and more cli apps on linux, and now (sadly) am starting to spend more time across both linux and windows (forced on windows due to work)...so it makese sense to consider a cross-platform shell.
- WorldMaker 4y ago
  Anecdotally, I haven't noticed too much pain in crafting cross-platform scripts in PowerShell 7+. Most of the platform differences I've seen in PowerShell are at the "module level" (library of "commands/cmdlets") and most commands that are in platform-specific modules generally are pretty obvious that they are platform-specific modules. A lot of modules are cross-platform. The biggest shift is learning to trust PowerShell commands/cmdlets and operators over platform-specific binaries like awk/sed/grep and so forth. A lot of those tools and manipulation steps can be done with native PowerShell commands/cmdlets/operators, but it's definitely a journey to thinking in PowerShell terms (that the linked repo looks like it can help with) and using/trusting its object-based tools, especially if you are used to the extended Linux shell text manipulation tool chain as "conversion" between the two paradigms isn't always straightforward.
  - mxuribe 4y ago
    Aaahhh, ok, i understand now. Thanks alot; very, very helpful!

mxuribe 4y ago

I'm curious....are the shortcomings that you encounter the types where elements of your scripts need to differe between Mac, windows, and Linux? I ask because i really don't like powershell...but am crafting more and more cli apps on linux, and now (sadly) am starting to spend more time across both linux and windows (forced on windows due to work)...so it makese sense to consider a cross-platform shell.

WorldMaker 4y ago
Anecdotally, I haven't noticed too much pain in crafting cross-platform scripts in PowerShell 7+. Most of the platform differences I've seen in PowerShell are at the "module level" (library of "commands/cmdlets") and most commands that are in platform-specific modules generally are pretty obvious that they are platform-specific modules. A lot of modules are cross-platform. The biggest shift is learning to trust PowerShell commands/cmdlets and operators over platform-specific binaries like awk/sed/grep and so forth. A lot of those tools and manipulation steps can be done with native PowerShell commands/cmdlets/operators, but it's definitely a journey to thinking in PowerShell terms (that the linked repo looks like it can help with) and using/trusting its object-based tools, especially if you are used to the extended Linux shell text manipulation tool chain as "conversion" between the two paradigms isn't always straightforward.
- mxuribe 4y ago
  Aaahhh, ok, i understand now. Thanks alot; very, very helpful!