4 ms·

I would argue the object approach limits the universality of the PowerShell way as a general purpose computer interface because it binds it to the necessity of

I would argue the object approach limits the universality of the PowerShell way as a general purpose computer interface because it binds it to the necessity of a particular flavor of object system (e.g. .Net) and mutable data which is venom to general purpose pipe and filter systems. jq looks very interesting though note that it builds upon an underlying notion of text to serialize JSON.

Canada 11y ago
You can parse streams of text in PS too, so it's not like cmdlets are making the pipeline any less powerful. As for binding to .NET, I don't think that's very limiting. A surprising amount of stuff is already easily hosted in .NET. I would argue that all PS needs to be more competitive is: Ports to Linux/*BSD/OSX and a terminal implementation for Windows that doesn't suck. Cmd.exe is a piece of shit that needs to die: - Command editing. Is support for at least ^A, ^E, ^W, and friends too much to ask? - Completion. Who wants to cycle through 4253 possibilities one at a time? - Copy/paste. Programs actually STOP executing when you select text, like as if you ^Z in Unix. Even with quick edit enabled so you don't have to ALT-SPACE-E-ENTER<select stuff>ENTER, the fastest way to paste is 4 keys: ALT-SPACE-E-P. - No SSH. Microsoft is addressing this. It's borderline criminal that Windows doesn't just ship with OpenSSH server already. - No screen/tmux. I can't even talk about how it deals with resizing without using a lot of profanity. - Lack of echo by default is seriously annoying. In short, make the terminal feel like Putty and the editing/completion features feel like bash and I think PS could give all existing shells a run for their money.