2 ms·
I found this a weird post. The shell does know what files are (how else could you do "echo * "?) and programs do take arguments and have return values. In any
by icebraining 11y ago
I found this a weird post. The shell does know what files are (how else could you do "echo * "?) and programs do take arguments and have return values.
In any case, I think the author is kind of tilting at windmills; as far as I know, that Unix and Linux don't really follow the Unix philosophy is reasonably accepted today, even if it wasn't back in '83, when Rob Pike and Brian Kernighan made the presentation called "UNIX Style, or cat -v Considered Harmful", which pointed out exactly those problems, which were already in development:
Bell Laboratories
Murray Hill, NJ (dec!ucb)wav!research!rob
It seems that UNIX has become the victim of cancerous growth at the hands of
organizations such as UCB. 4.2BSD is an order of magnitude larger than Version
5, but, Pike claims, not ten times better.
The talk reviews reasons for UNIX's popularity and shows, using UCB cat as a
primary example, how UNIX has grown fat. cat isn't for printing files with line
numbers, it isn't for compressing multiple blank lines, it's not for looking at
non-printing ASCII characters, it's for concatenating files.
We are reminded that ls isn't the place for code to break a single column into
multiple ones, and that mailnews shouldn't have its own more processing or joke
encryption code.
Rob carried the standard well for the "spirit of UNIX," and you can look
forward to a deeper look at the philosophy of UNIX in his forthcoming book.
Yet, Rob Pike himself uses Linux nowadays - the problem today isn't so much acceptance, but backward compatibility.