drfuchs

Interesting to note that the original invention of Proof Of Work was motivated by anti-spam in particular ("Pricing via Processing or Combatting Junk Mail" Dwork & Naor, Advances in Cryptology — CRYPTO' 92).

Us Americans (pun intended) have no idea what “vignette” means in this context. And our dictionaries don’t, either.

Well, I'm #4, but it's all from TeX stuff (where I'm kind of a ringer), and not The Art Of Computer Programming. The beyond-amazing Udo Wermuth is also all TeX, I believe, and did it without having a home team advantage; everyone else high on the list looks to be strictly TAOCP.

The first episode of Star Trek: The Original Series where we hear the ship's computer speak is "Mudd's Women" filmed starting June 1966. UFO had SID talking from the very first pilot, filmed starting April 1969. So, less than three years apart, and not much time for the public's perceptions to change. On the other hand, HAL showed up on screen in the interim, so maybe that helped. And big shout out to Lost In Space's Robot B9, with more personality than all of them put together, and who showed up before for all of them, in 1965.

Let's keep this pertinent to Hacker News: The nicely intoned computer voice of SID on UFO was way more advanced than the clunky monotone of the Star Trek TOS ship's computer.

See the 1949 Ealing Studio film “Passport to Pimlico” for a take on how it’s going to work out.

A favorite Knuth story to illustrate: He was re-writing the 8080 code for the processor that ran our new Alphatype CRS Phototypesetter, since the manufacturer's code wasn't suitable. Real-time, 7 levels of simultaneous interrupt stuff, since it controlled two stepper motors that moved the lens around the photographic paper, plus four custom font outline-tracing S100 cards that flashed vertical segments of characters at just the right moment on the CRT that the lens then focused onto the paper. No debugability other than a 4x4 keyboard and a 15(?) character display. I was responsible for the code on the other end of the RS232 port that connected it to the DEC mainframe, sending down character outlines on the fly to the very limited memory on the 8080, along with the properly-sorted character placement info ultimately from TeX.

Anyway, we'd been doing morning, noon, and night debugging sessions together for a number of days. On maybe the 3rd morning, I arrived at his office and was speaking with his secretary of many years, Phyllis Winkler, when Knuth came in. He handed her a stack of maybe a dozen or two pages, saying "Here's a paper I wrote; please type it in." When? When did he write it? It's still a mystery to me.

Can I decode my DVD collection now?

TeX was developed on DECsystem-10/20 machines (36-bit words, your choice of byte size). The various operating systems (Tops20, Sail/Waits, ITS) were superior to Unix in a few ways, one of which was that when a process was suspended (think control-Z, or even control-C) you could issue the built-in shell SAVE command that would save the entire state of the suspended process into a new executable, data segment as well as code. So, on these systems, you could run TeX, have it load a bunch of macros and such, and then SAVE the result as a real, pre-configured executable for the world to run. Easy-peasy.

This was true for the original TeX78 written in Sail, as well as the ultimate TeX82 written in Knuth's WEB macro language on top of Pascal (that nowadays typically gets transpiled to C). Other programs did similar stuff; the feature was in the OS way before TeX started.

(Gory detail: Actually, TeX went a little further, to free up all possible address space for the final executable: The version that could initialize various hash tables and hyphenation trie tables could dump (nee serialize) a binary file of the resulting data structures; then a slimmed-down version that didn't have that code would read the binary info back in to recreate the initial data structure state, and that's what you'd SAVE the production executable from.)

For the unix-y versions of TeX, there was effort made to mimic this sort of thing in user-land with "undump", but admirable as it was, it was a hack, I'm told. These days, everything is so fast, it's not clear that this feature would be worth it anyway.

Source: me; I was there.

Wait til you see the DigiComp II! It has flip-flops driven by marbles and gravity. Truly astounding.

Hey, DVI was my suggestion and initial implementation; Knuth's comments in the TeX source code acknowledge this, and they mention plenty more people than Frank Liang who made significant contributions to TeX82: Leo Guibas, Michael Plass, Lyle Ramshaw, Robert Sedgewick, Luis Trabb Pardo, Howard Trickey, Doug Wyatt, and Ignacio Zabala.

Also, Nixie Tubes were absolutely not “tiny.” Typically, they were about the same size as a vacuum tube you’d find in the back of your radio or TV. They were universally used on electronic equipment; less so on consumer devices.

Nope, that would be Michael Plass (thesis title: "Optimal pagination techniques for automatic typesetting systems," though his line-breaking work is what showed up in TeX) and Frank Liang ("Word Hy-phen-a-tion by Com-put-er"). I wasn't there yet.

Metafont users can specify point size, boldness, slant, and whatever other parameters they choose (plus device-specific info like resolution) that can then be used in the simultaneous equations that determine the coordinates of critical points and shapes of pens used to draw the characters. So, for the smaller-font issue, the width of the pen may be a non-linear function of the font point size; ditto for the x-height, etc. In Metafont, it's the responsibility of the font designer / coder to handle it all; there's no automated algorithmic monkeying with the pixels other than what you write. This all becomes much clearer with a perusal of The METAFONTbook.