Conversation

Notices

1. Verius (verius@community.highlandarrow.com)'s status on Sunday, 05-Nov-2017 12:47:31 EST Verius
   Whenever I try a bit of powershell it strikes me that it's in a bit of an uncanny valley of shellness. Unix shells work because unix programs are traditionally written with the shell in mind. Windows programs have traditionally not been written that way.
   
   Powershell's solution is to focus on .NET assemblies instead of on programs. But using OO from powershell is awkward, it's possible but not as easy as from C#.
   
   Meanwhile the scripting aspect of Powershell is both underdocumented and really rather awkward.
   
   It feels like Powershell is trying to combine two things: exploratory bashing (i.e. writing for loops on the command line) and scripting and is succeeding at providing a pleasant environment for neither.
   1. Verius (verius@community.highlandarrow.com)'s status on Sunday, 05-Nov-2017 12:51:34 EST Verius

      in reply to
      I would say that an approach like http://scriptcs.net/ is much better for scripting. For command line script bashing the ability to quickly execute F# programs could be much better. In command line script bashing in my experience you're using a mixed procedural / functional paradigm (for loops and pipes) and F# really isn't all too bad for that.