3 ms·
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 greppi
by 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 agoCombining 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?