| PowerShell is supremely explorable. All you need to get started is knowledge about a few cmdlets. Get-Help, Get-Member, Get-Command and Get-Alias then you are in business. There is nothing about PowerShell that cannot be discovered through those 4 cmdlets. If you frequently need to dig down to .NET you are doing it wrong. Contrary to your previous assertions, PowerShell was designed for REPL from the outset, and it achieves that much better than any Unix/Linux shell, bar perhaps fish. PowerShells commands (cmdlets) are inherently rich on metadata. You cannot create a cmdlet without exposing metadata which is then used by the shell to drive automatic type coercion, syntax charts in help as well as tab completion. It is so intrinsic to the concept, that you'll automatically get tab completion for your own functions, and even for your own script files. PowerShell was definitively NOT designed as an RPC layer. You claim to "know PowerShell probably better than most people", and yet you are unaware that PowerShell was specifically designed as a hostable engine. It is hostable precisely because Microsoft wanted to have reusable script engine which could be used in-process (!) in administrative GUIs. Unlike traditional shells, PowerShells cmdlets share memory space with the host (the shell when used as REPL) because it SHOULD NOT use RPC to manipulate objects. You frequently use "appeal to authority" arguments, but the substance of your posts gives you away. You are certainly no expert on PowerShell. |