On Sat, 2008-09-27 at 12:04 +0200, Emanuel Rumpf wrote:
Still in planning stage, but maybe not that far away:
Solutions of simple problems, demanding several complex packages to be
> piped into one each other, does not take my fancy.
Well... some unix
gurus would claim here that unix
piped *simple command tools* i.o. to accomplish *complex tasks*...
depends on the vew ;-))
Maybe I was a a bit too harsh? There certainly are times when all you
care about is getting the job done quickly as well as correctly. A UNIX
guru/sysadmin will often be confronted with unique questions like: -
Where the f*** did I misplace that shit and how to incorporate it into
our new database from <insert vendor>, which we are gonna live with for
the foreseeable future ...
The next time "shit happens", it will be a different situation, craving
for yet another new approach. And it can most probably be solved once
more by using standard tools.
At home I have bits and pieces of audio related stuff that is not really
working the way they were intended (yet.) They are all written as
typical unix filters, the one piping into the next eventually arriving
at either ALSA or OSS. This is for prototyping and evaluation of ideas.
Real applications loops around similar ideas, but on a scale of every
damned millisecond rather than the relaxed ALSA defualt of a second or
This is where that other idea from K&R comes into play. Real unix
systems comes with a C-compiler that will optimze and vectorize your
scribblings into something that is actually useful.
I haven't dared to open the link you provided, but given past
experiences, by the time I realize that the world is going to the dogs,
my friends hardly raises an eyebrow and only says: - "We told you so!"