Announcing TermKit [LWN.net]

Announcing TermKit

Posted May 18, 2011 13:53 UTC (Wed) by rfunk (subscriber, #4054)
Parent article: Announcing TermKit

I have mixed feelings about this... there are a lot of good ideas here (some of which have been tried before), and maybe it could catch on. Maybe it's time to advance the state of the art in command-based computer interaction. But the discussion of pipes and standard I/O seems to miss the point entirely about the benefits of the Unix pipe model.

to post comments

Announcing TermKit

Posted May 18, 2011 20:49 UTC (Wed) by elanthis (guest, #6227) [Link] (1 responses)

How so?

More importantly, are the benefits of the UNIX pipe model worth all the cons of the model?

Having been doing this some 15 years, I'm heavily inclined towards doing things the TermKit/PowerShell way. It's just better. And nothing says that the classic UNIX model doesn't still work (in fact, it quite explicitly does). It just functions at a reduced state due to its inadequacies.

Announcing TermKit

Posted May 18, 2011 23:07 UTC (Wed) by jonabbey (guest, #2736) [Link]

As nye said, it's all about the network effects. If you can get all these tools to converge on a structured schemata for pipeline communications, great. Not easy to do, though.

Right now it seems that things in Linuxland are divided between ASCII tooling at the command line, D-BUS at the system level, and XML, HTML, and JSON at the network level.

I can't think of any faction in our community working today with the power to unify and move past all that.