Robert M. Pirsig "Zen and the Art of Motorcycle" dies at 88
Publison
Posts: 12,366
I know this author has been named many times her. I think Heather brought him up first.
http://www.npr.org/sections/thetwo-way/2017/04/24/525443040/-zen-and-the-art-of-motorcycle-maintenance-author-robert-m-pirsig-dies-at-88
http://www.npr.org/sections/thetwo-way/2017/04/24/525443040/-zen-and-the-art-of-motorcycle-maintenance-author-robert-m-pirsig-dies-at-88
Comments
-Phil
So many years since I read that.
I will have to read it again. Just now I reading that it's about motorcycles and road trips across the USA. I remember it being about philosophy...
If you read this as philosophical nonfiction then it's pretty heavy - a descent into madness (obsession with MoQ) and recovery. A recommendation perhaps to stay to the middle path? But on a more geeky note...
From Lila:
This one sounds like it might be from "From NAND to Tetris" ;-)
The list is not small. Take a look at the instruction set manuals of our computers today. They are gigantic. Be they Intel x86 architecture or ARM. How many pages do you think it will take to describe the P2 instruction set?
Even back in the days of 8 bit computers the hardware guys put hundreds of instructions into the Z80 instruction set that the software guys never used!
Seems to me that for 5 decades or so that disconnect between what the hardware guys think a machine should provide to software and the software guys expect from hardware has caused lots of problems.
I point to the Intel 432 architecture, and the Intel 860 and the Intel Itanium as examples of failed mismatches between the hardware and software abstractions. There are many others outside of Intel.
What that quote is hinting at is the RISC idea. A Reduced Instruction Set Computer whose hardware only provides instructions that compilers can be expected to use.
That has culminated in the RISC V instruction set. Which can indeed be written on a single page.
My point here is, I guess, that somewhere along the line it is necessary for programmers to know something of hardware design. And it is necessary for hardware technicians to know something programming.
At least enough on both sides that they can make a simple and efficient abstraction layer between hardware and software. The instruction set that is.
It has been a long road.
That's from Pirsig's LILA. He was a technical writer for a while, but I'm not sure which computers he worked on. His main point is how layers of abstraction work. When you're using a flip-flop then you're probably not thinking too much about the transistors that make it up. (Unless you violate the timing parameters, or environmental specifications.) Etcetera. When you're writing the Tetris app you're probably not worried about NAND gates.
But to your point there has been some interesting security research that results in things like Rowhammer.js and then ...
I've also read his other book, Lila, which I enjoyed, but it didn't make such a lasting impression on me as Zen.