3 ms·
I'm using a large corpus of Powershell scripts, mostly written by enthusiastic Microsoft consultants, and even if I know exactly what they do I cannot stand the
by HelloNurse 10y ago
I'm using a large corpus of Powershell scripts, mostly written by enthusiastic Microsoft consultants, and even if I know exactly what they do I cannot stand the mysterious imports, the sequences of script invocations and bare statements that leave the session with the desired invisible state (and, conversely, closing and reopening the session after every major command just in case), the automagical option handling, and so on.
- Karrot_Kream 10y agoTo play devil's advocate, UNIX sh shell scripts are pretty mysterious too, and often leave the local environment polluted and other such no-nos.
- HelloNurse 10y agoEnvironment variables (and files) are very easy to inspect and change, the invisible bunch of objects in a Powershell session are not.
- btschaegg 10y agoThat's my impression, too. It offers a really nice feature set and surely is the one piece of windows you can get the most done with out of the box. But boy is it ugly. And the worst thing is that all the really nice functionality .NET provides with LINQ is implemented halfway at best, if at all...