3 ms·

Are there any currently-supported versions of Windows that don’t support Powershell Core? I recall installing it on Windows 2012, even. > Say what you want abo

by JoBrad 2y ago

Are there any currently-supported versions of Windows that don’t support Powershell Core? I recall installing it on Windows 2012, even. > Say what you want about bash, at least it doesn’t pull stunts pile that. I guess it depends on what you consider to be included in the terminal’s domain? There are entire papers and guides on which commands are considered safe (sometimes only when run in a very specific way), and which variants, alternatives, etc. you should use instead, for Bash scripts, because of the inconsistency in what a command evaluates, does, and returns for various distros. That’s not to hate on Bash, but just to point out that it’s not a strength of Bash vs PS.

sllabres 2y ago
When Powershell was first released I was primarily working with Unices and was very curious what would work better: The Unix way in cutting, changing and grepping some part of stdout (in some OS a bit simplified b with options for automated pricessing which commands the programm to output colon delimited or otherwise formatted) Or the Powershell way where on can access data members directly. I thought I would prefer the second method more, because the access looked much cleaner/structured. But after all these years (still mostly Unix scripting but Powershell and some other environments too) my mind has changed. Would like to hear what others would prefer' Unix method with some scripting language or windows method with Powershell)
- chaps 2y ago
  Combining both powershell and unix is neat!
- justsomehnguy 2y ago
  > The Unix way in cutting, changing and grepping some part of stdout And this is exactly the problem. You no longer have en_US as a locale? Have some titles lounger. You no longer have en locale at all? Have an greška instead of error. Oh, you the schmuk who don't agrees to use the best units in the world, totally retarded and "bUt iF yoU WriTe THe dATe as in the journal..."[0] but freedom ones? No longer accept 13 as an hour. Like come on, every idiot knows there is no such thing as an 13th hour! Oh, you added an additional column to help your busniessor whatever? Your sEd MagIK gone to hell. Should I continue? [0] when was the last time you actually wrote multiple documents so you can actually benefit from MMM-dd?
akira2501 2y ago
> because of the inconsistency in what a command evaluates, does, and returns for various distros. I'm not aware of any difference in bash between vendor distributions for which this is true.
- nrr 2y ago
  It's less of a problem in today's Linux monoculture, but I actually initially learned Perl and Tcl precisely because of subtle incompatibilities between systems for tools like sed and awk, not to mention utilities like ps and tar.
  - larntz 2y ago
    This may not count because it's not bash specifically or even Linux -> Linux, but one place you might run into this is running scripts between Linux and Mac/BSD. In the past I've seen bad things happen because a script was written by someone on OSX that gets run on a Linux (GNU) based system. Two common examples are the `sleep` and `sed` commands. Edit: I meant to reply to the parent comment.

by JoBrad 2y ago

sllabres 2y ago

When Powershell was first released I was primarily working with Unices and was very curious what would work better: The Unix way in cutting, changing and grepping some part of stdout (in some OS a bit simplified b with options for automated pricessing which commands the programm to output colon delimited or otherwise formatted) Or the Powershell way where on can access data members directly. I thought I would prefer the second method more, because the access looked much cleaner/structured. But after all these years (still mostly Unix scripting but Powershell and some other environments too) my mind has changed. Would like to hear what others would prefer' Unix method with some scripting language or windows method with Powershell)

chaps 2y ago
Combining both powershell and unix is neat!
justsomehnguy 2y ago
> The Unix way in cutting, changing and grepping some part of stdout And this is exactly the problem. You no longer have en_US as a locale? Have some titles lounger. You no longer have en locale at all? Have an greška instead of error. Oh, you the schmuk who don't agrees to use the best units in the world, totally retarded and "bUt iF yoU WriTe THe dATe as in the journal..."[0] but freedom ones? No longer accept 13 as an hour. Like come on, every idiot knows there is no such thing as an 13th hour! Oh, you added an additional column to help your busniessor whatever? Your sEd MagIK gone to hell. Should I continue? [0] when was the last time you actually wrote multiple documents so you can actually benefit from MMM-dd?

akira2501 2y ago

> because of the inconsistency in what a command evaluates, does, and returns for various distros. I'm not aware of any difference in bash between vendor distributions for which this is true.

nrr 2y ago
It's less of a problem in today's Linux monoculture, but I actually initially learned Perl and Tcl precisely because of subtle incompatibilities between systems for tools like sed and awk, not to mention utilities like ps and tar.
- larntz 2y ago
  This may not count because it's not bash specifically or even Linux -> Linux, but one place you might run into this is running scripts between Linux and Mac/BSD. In the past I've seen bad things happen because a script was written by someone on OSX that gets run on a Linux (GNU) based system. Two common examples are the `sleep` and `sed` commands. Edit: I meant to reply to the parent comment.