Imagining the CLI For the Modern Machine 317
scc writes "TermKit is a re-think of the storied Unix terminal, where human views, input and data pipes are separated. Output viewers render any kind of data usefully. It may not be a new idea, but it's certainly a new take on it." I know you are quite comfortable in your shell of old, but this sort of thing sure gets my juices going. The best of both worlds.
Re:Mac only. (Score:5, Informative)
Re:PowerShell (Score:1, Informative)
Actually, this is quite straightforward copy of PowerShell. It looks like they ported Microsoft PowerShell to Mac. Fantastic.
Re:Everything is an INCOMPATIBLE object (Score:2, Informative)
Except that in PowerShell all of the objects are reflective and automatically have a textual representation, even if one is not provided by the author.
Being reflective you can also see the data structure instantly, clearly defined by type, even if the author never wrote any documentation. Moreso, as all programs are similarly reflective, you can tell all parameters that it can accept as well as all data that it can return without documentation.
PowerShell programs are fully capable of streaming text as well as intermixing object streams with text streams.
As you can in PowerShell.
As you can in PowerShell, except that you don't have to concern yourself with additionally parsing and reformatting those text streams in order to allow them to be consumed. Moreso, as virtually all of the object models that exist within Windows is available within PowerShell as objects, including WMI, LDAP, COM and .NET, you can combine disparate libraries into a single command line treating all objects as equals and without having to write any additional plumbing code.