3 ms·
> mit vs. GPL By this measure, we shouldn't be using X or Wayland because they're MIT. > pipe-and-filter vs loaded DLLs At first I didn't understand what you
by sidpatil 4y ago
> mit vs. GPL
By this measure, we shouldn't be using X or Wayland because they're MIT.
> pipe-and-filter vs loaded DLLs
At first I didn't understand what you were referring to, but I realized you were talking about cmdlets. In that regard, PowerShell is more like a scripting language than it is like a traditional Unix shell.
The more "Unix-like" approach would be to write thin command-line wrappers around the libraries you want to use. If I'm not mistaken, this is how projects like LAME and FFmpeg are implemented.
- oaiey 4y agoRegards the licencing: you are right. I was a vit blinded by the core gnu tools. Tiny wrappers do not work since .NET, while being very Performanz will never be C like tiny.
- sidpatil 4y ago> Tiny wrappers do not work since .NET, while being very Performanz will never be C like tiny. I meant tiny wrappers around non-.NET libraries, to approximate the functionality you get in PowerShell in a traditional UNIX shell.