I beg to differ:
http://www.art.net/~hopkins/Don/unix-haters/handbook.html
> pipes, scripting C programs, etc.
None of these things are necessary when every piece of information on your machine lives in a Lisp world image. As it should. And would, if the machines we are now using were the descendants of real computers, rather than of early-1980s children's toys.
http://www.jwz.org/doc/worse-is-better.html
"None of these things are necessary when every piece of information on your machine lives in a Lisp world image."
http://www.artima.com/weblogs/viewpost.jsp?thread=24807
And your last link would be applicable, save for the "ocean" actually having been "boiled" in this manner. The Lisp Machine existed. You cannot un-create it. It proves that all of the supposedly impossible or impractical pipe dreams of the Unix haters are in fact possible.
So, C is better than Lisp, depending on your metrics.
As for the ocean, it is no longer the machine on which you are typing your program. It is all of the information, data, and code available to you on Internet. That's a lot of ocean to boil. Any Lisp needs to work well with as much of it as possible to be considered a useful language today.
A camel is also a better vehicle than a truck, depending on your metrics. (Quite seriously.)
But why is this a desirable dream? It seems to suggest no other languages or technologies have any merit, except Lisp. Unix and C are brilliant pieces of work, and Lisp's hang up of refusing to work well with them really set Lisp back. Compared to, say, Perl, Python and Ruby which really embraced Unix concepts (pipes, scripting C programs, etc.).
I happen to think the JVM is a nice piece of work, too, and I'm happy to see a Lisp that works seamlessly with it and benefits from its strengths. Cooperation and interoperability are good things.
"which Reeketh of the Cube Farm."
Cube Farm coders deserve good programming languages, too.