Heater wrote: ↑Tue Sep 12, 2017 10:49 am
Djarid,
Pipelining entire objects instead of just the stdout alone is sufficient to want to have this in raspbian.
CecilWard,
The object pipeline thing is so sensible.
Could either of you tell me how pipelining objects in shell commands is in anyway useful on an OS where none of the programs that run on it support piping objects in or out?
In fact can you give me an example of when piping objects is useful ?
To my mind the ultimate simplicity of Unix pipes just shoveling byte streams around is one of the main strengths of a Unix system. One can connect anything to anything even if those programs were developed independently and have no knowledge of each other.
If I want to pipe objects around I can overlay that on top of Unix pipes by using JSON format or Protocol Buffers or whatever I like.
Hi. Long time raspberry-pi noodler, first time poster (in my other bag at home I still have my model B with 256 MB RAM, and I have a Zerow W in my everyday bag). I have five years experience using PowerShell day in day out for my job.
PowerShell (PS) is not, unequivocally,
better than Bash. For most of your typical Unixy tasks, Bash will perform far faster than the equivalent PS, while consuming far less memory and fewer cycles. But that doesn't mean an object oriented shell scripting language is useless. PS accepts stdin/stdout, so you can still use it with the existing Unix binaries you're used to. Essentially, you can still "connect anything to anything" with PowerShell in Linux, now including objects, and all the sanity they bring to structured data and more complex tasks.
If you read that and think, "Well why wouldn't I use Python instead?" then use Python. More options are better than fewer.
