PowerShell is fundamentally flawed system. The object oriented language does not belong to shell. It’s simply too verbose and awkward for repeated fast interact

PowerShell is fundamentally flawed system. The object oriented language does not belong to shell. It’s simply too verbose and awkward for repeated fast interactive use. When tons of commands starts with get-*, that’s 4 extra keystrokes before even you begin to specify actual command. I know there are shortcuts but still that’s workaround this bad foundation. A general purpose programming language where you write statement and it stays there and gets executed million times is very different model than shell language where you write statement, throw it away and move on with next. Combining both is creating Frankenstein that’s good at neither. It’s just quite funny that PowerShell syntax doesn’t allow == but does need curlies. Who in the world would have thought of that? Also the view that everything in shell should output structured data is plain wrong. Shell should output human readable formats. always. It’s tool’s job to do proper parsing and deal with related complexity. The convenience should always be afforded to humans, not tools. Even if one changes all built-in commands to comply this, vast majority of programs won’t. So lot of above leads to Frankenstein-ish design that looks like awkward hodge pudge of bandaids. While cross platform is good, MSFT needs to start brand new effort, leave PowerShell behind and take command line to next generation with right first principles.