There's nothing inherently linking the CRL to using objects within pipes. You could use for example JSON if you really wanted.
I'm not opposed to lifting ourselves above text over unix pipes, but I think that if we are going to do it then we should go in for the penny, in for the pound. Such a system will be incompatible with existing unix tools, so we might as well drop all the technical debt. I don't think powershell is a large enough break from the traditional unix setup.
Aside: I've noticed that there is an open source implementation of Powershell for Mono called `pash`. Does anybody use this?
You can complain that the increase in ABI complexity isn't worth the extra features, but I don't think it is fair to complain about increased ABI complexity, period.
If I want to write a unix utility in C, or Java, or C#, or Lua, or Racket, or postscript, or brainfuck..., I can. Not just in an academic sense, but in a "it is actually reasonable and trivial to do so" sense. The list of programming language implementations that cannot read/write to/from files (knowledge of the concept of "pipes" is unnecessary, the user's shell opens those) is vanishingly small.
For the average developer who just wants to use Powershell/bash/whatever, it is absolutely language lock-in.
You can also make use of any COM, DCOM, or plain dynamic library in the shell.
There are also text formatters for interoperability with older scripts.
Edit: Of course, you have the option of writing a minimal wrapper in PS that shells out to your other-language command but the interface between PS and non-PS programs is still based on a string commandline.
You can do IPC with PowerShell [1], but it's nowhere near as simple as UNIX-style piping.
[1] http://coders-corner.net/2014/05/11/inter-process-communicat...
If we are accepting that sort of languae lock-in, I'd rather get something like scsh off the ground.