Quoting [EMAIL PROTECTED], from the post of Thu, 06 Mar:
> >   cat  file  [|possible pipe] | lpr
> 
> I find their interface today more convenient to some tasks than the
> ASCII-alone world of pipes and command line).
> 
> UNIX command line tools are great for some jobs, but the computer world
> haven't frozen 30 years ago when these concepts where first invented.

last time I heard that was from a Microsoft guy at an EDA confference. a
guy got up in the audience (I later found out he was the head system guy
at VAResearch) and explained that there was nothing wrong with this very
natural model, it's the organic way to do things. people too have input
(mouth), pipes (points to his stomach) and outputs! (turns points to his
ass)

the point is, the right tool for the right job. I agree plugins are
great, and I agree the CLI pipeline is not too "smart" in many cases to
serve all the needs, but forking to a new process with several file
descriptors (not just the one) is a pretty good plugin interface, and
all you have left to do is decide on a protocol. the two ideas are not
THAT remote if you generalize plugins (SOAP?) and make commandline
piping stronger (two way or more).
-- 
Supreme being of leisure
Ira Abramov

http://ira.abramov.org/email/ This post is encrypted twice with ROT-13.
Documenting or attempting to crack this encryption is illegal.

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to