3 ms·
(I started writing this comment when the submitted title was “The Summer Of 1960 (Time Spent with don knuth)” and the url was specifically the section http://ed
by svat 6y ago
(I started writing this comment when the submitted title was “The Summer Of 1960 (Time Spent with don knuth)” and the url was specifically the section http://ed-thelen.org/comp-hist/B5000-AlgolRWaychoff.html#7 http://ed-thelen.org/comp-hist/B5000-AlgolRWaychoff.html#7 , but it still applies I guess.)
There's a PDF version at https://www.computerhistory.org/collections/catalog/102724640 https://www.computerhistory.org/collections/catalog/10272464... which incidentally is a scan from a copy given to the Computer History Museum by Donald Knuth himself — before the title “Stories about the B5000…” he has added, in pencil, “Half-true”. :-)
Knuth tells his side of this story in video 27 (of 97) of his Web of Stories oral history: https://www.youtube.com/watch?v=QeiuVNDQg4k&list=PLVV0r6CmEsFzeNLngr1JqyQki3wdoGrCn&index=28 https://www.youtube.com/watch?v=QeiuVNDQg4k&list=PLVV0r6CmEs... — transcript (thanks to https://github.com/kragen/knuth-interview-2006 https://github.com/kragen/knuth-interview-2006):
> Some people from Thompson Ramo Wooldridge approached me and said, Don, we understand that you can write compilers. We’re going to put in a proposal to Burroughs to write a compiler for their machine, the Burroughs 205, for a language called ALGOL, which was just being invented at that time […] made a proposal to Burroughs for I believe it was $70,000, to create an ALGOL compiler for the Burroughs 205. The people who made this proposal really, though, were clueless about how to write compilers, so they hired me, a Case senior, to do the job, because they had heard that I knew how to do it. I had done this RUNCIBLE and a couple of versions of other software at Case, […] but Burroughs turned them down; they didn’t give them the contract.
> So after Burroughs said no, […] maybe I’ll write to Burroughs on my own, and I sent them a letter and said, I’ll, you know, for $5,000 I can write you an ALGOL compiler. Now $5,000 was a huge amount of money in 1959, 1960. I mean a college professor was making $8,000 a year or something like this. So I thought $5,000 was an incredibly rich thing, you know, to do. […]
> […] I spent the summer writing this compiler for ALGOL, for the Burroughs 205, and I wrote it, but really I had it only in pencil and paper, I didn’t have it ready to go, and then I would take it with me on, as I went out to Pasadena, and work on it there when I was at the Burroughs plant in Pasadena.
> So on my way out West; I had a little Volkswagen, that I had gotten from my parents, and I drove 100 miles a day, and got a motel, and sat down, and wrote code, wrote software, and took 30 days to drive from Milwaukee to Pasadena, every day writing a little bit of this software. Then I got to Pasadena, and had all my code, had all my notes, and started putting it on to punched cards, and you know, debugging it and by Christmas time I had their compiler for them […] I heard for the next ten years that people in Brazil were still using it a lot.
> And so it was a, it was an interesting experience for me, but the most important, from my point of view, was I had $5,500, which was enough to get married. And so in the summer of ‘61 Jill and I got married, and it paid for our honeymoon trip in Europe, which was our first time seeing the world.
The actual compiler “source code” (written in pencil, assembly language and flowcharts) seems to be this one: http://archive.computerhistory.org/resources/text/Knuth_Don_X4100/PDF_index/k-2-pdf/k-2-c1039-ALGOL-B205.pdf http://archive.computerhistory.org/resources/text/Knuth_Don_...
There's also 43-page “documentation” of the compiler http://archive.computerhistory.org/resources/text/Knuth_Don_X4100/PDF_index/k-2-pdf/k-2-u2435-B205-ALGOL-internals.pdf http://archive.computerhistory.org/resources/text/Knuth_Don_... which starts with “How does this compiler work? Frankly, it's a miracle if it does”.
Also in the same interview, he reveals something about how he ended up getting a master's degree (as mentioned in the story here):
> […] second half of my freshman year, I started having a little problem with my grades, and so I had to give up ping-pong.
> But starting in my sophomore — junior year, I found out that you could take graduate courses at Case, and they were easier than the undergraduate courses. The reason is that Case had really strict admissions requirements for undergrads, but they were fairly loose about admitting graduate students. […]
> And as a result, I had accumulated also, by the time I was a senior, I had accumulated lots and lots of graduate credits. Now, as a result then, Case did, on Graduation Day, Case did an unprecedented thing that had never been done before, they awarded me a Master’s Degree, simultaneously with my Bachelor’s Degree. And this, the faculty had gotten together and [voted] unanimously that this should happen, and I remember, you know, that was another thing that got into the newspapers at the time […] I had taken these graduate courses because they were easier. I didn’t, I don’t know if I’ve ever told anybody else this before today, but that was one of the reasons I could do so many other things.
- yellowstuff 6y agoI feel like driving from Milwaukee to Pasadena 100 miles per day is the most Donald Knuth thing ever. IE, a huge task completed in the slowest and most deliberate way possible.
- svat 6y agoHa! I imagine the point was to spend a month writing the program mainly, while also doing a little driving during breaks. (BTW it appears that Milwaukee to Pasadena is about 2000 miles now, which works out to even less: ~70 miles a day. Or given that the interstate highway system was less developed in 1960, maybe it really was about 3000 miles then.)
- rurban 6y agoIt was a Volkswagen. In Summer. Through the desert probably. The cooler overheats constantly. You stop at every gas station, and you'd be lucky if there was one every 100 miles.