3 ms·
PowerShell does something similar to what you're describing, but arguably better. With PowerShell, instead of passing text strings between programs, you actual
by toomanybeersies 9y ago
PowerShell does something similar to what you're describing, but arguably better.
With PowerShell, instead of passing text strings between programs, you actually pass CLR objects between programs.
PS does a lot of things very nicely, it's a great tool for Sysadmins, with more safety than Bash. The verbose syntax (e.g. Get-ChildItem vs ls) is a big stumbling block the few times I've used PS, but it makes sense from the point of writing a script to be executed more than once, it's a much more readable language than Bash.
- deathanatos 9y agoI'm a Linux user (my Windows days predated Powershell), so I'm unfamiliar here. I think the biggest concern such a setup gives me would be: 1. is whatever encoding the CLR uses for IPC efficient enough for all purposes? 2. can you stream objects / push multiple objects? (some programs, such as tar, generate potentially massive amounts of output that you cannot buffer) Otherwise, that actually sounds a good deal stronger than my initial suggestion, and potentially a lot more powerful. (I think I just wonder about its generality & performance.)
- fowl2 9y ago1. It's mostly in-process. 2. Yes, there's a "pipeline" concept. It's a quite a... quirky language, but you can[2] do pretty much anything down to calling C functions, etc. PS. PowerShell is on Linux now too[1] [1] https://azure.microsoft.com/en-us/blog/powershell-is-open-sourced-and-is-available-on-linux/ https://azure.microsoft.com/en-us/blog/powershell-is-open-so... [2] You probably shouldn't.