Python is no where near Lisp in code as data. Also, I think what's important is to marry the Lisp programming language and the Lisp Machines. The hardware was b

Python is no where near Lisp in code as data. Also, I think what's important is to marry the Lisp programming language and the Lisp Machines. The hardware was built with Lisp in mind. I am a fifth of the way through a 1991 book called "The Architecture of Symbolic Computers" by Peter M. Kogge, and it is like my eyes have opened wide. No more splitting hairs over Ruby, Python, Clojure, Linux, OSX and Windows: Give me a machine tailored for the software running on it. the Von Neumann register-based machine cannot efficiently serve all, it bottlenecks. People talk about Linux as the break away from the Windows and Mac OS crowd, but let's face it, it is all the same thing running on Von Neuman architecture hardware. There are people trying to build machines from scratch to run their own OS on. I hope somebody succeeds. I don't think we need to go back to Lisp Machines, but there's a lot of gold nuggets there to mine and re-use. Technology doesn't age linearly. Sometimes things are forgotten, and need to be rediscovered for progress to jump again. I work in Common Lisp (SBCL, LispWorks), Racket (Scheme), and I play with PicoLisp (incredible for its size). Shen is something I am trying to wrap my head around (optional typing, and optional laziness, functional, pattern matching, and there implementations of the small instruction set it runs on for many common languages - CL (SBCL), Java, Ruby, Python, JavaScript, Haskell, Clojure... Here's to the coming hardware revolution!