I think that's something every programmer dreams of sooner or later. It seems like anything I've worked on that's larger than a utility script eventually results in fudging around with multiple tools trying to get them to cooperate.
And every time, I'm like "I've got some fing code and they've given me some fing code and all I want is for them to run together."
Powershell can call code in .Net assemblies and I imagine there's a way to pass C# or some other .Net code in but it probably requires a fat command.
The true beauty here, I think isn't just the way the Command Line acts as an interpreter but that all the code on the system is exposed at all times through a simple, common interface.
Right? Imagine if you wanted to, I dunno, render HTML in a window in your application for some reason, and you could just easily pull up the running copy of Firefox on your system and call one of its functions, in real time, in your application. Done, now you've got an HTML renderer in your software.
You can actually do that in most modern GUI toolkits. It's usually called something like a WebView widget. See also the Chromium Embedding Framework. None of these talk to a separate running browser, to be fair.
And every time, I'm like "I've got some fing code and they've given me some fing code and all I want is for them to run together."
Powershell can call code in .Net assemblies and I imagine there's a way to pass C# or some other .Net code in but it probably requires a fat command.
The true beauty here, I think isn't just the way the Command Line acts as an interpreter but that all the code on the system is exposed at all times through a simple, common interface.