4 ms·
Cathode ray tubes were also used as RAM in early computers: https://en.wikipedia.org/wiki/Williams_tube https://en.wikipedia.org/wiki/Williams_tube One of the
by greenyoda 8y ago
Cathode ray tubes were also used as RAM in early computers:
https://en.wikipedia.org/wiki/Williams_tube https://en.wikipedia.org/wiki/Williams_tube
One of these computers was the machine at Manchester that Alan Turing worked on:
https://en.wikipedia.org/wiki/Manchester_Baby https://en.wikipedia.org/wiki/Manchester_Baby
- xellisx 8y agohttp://www.piclist.com/techref/mem/neonlamp.htm http://www.piclist.com/techref/mem/neonlamp.htm
- bjackman 8y agoThere's one of those* on display in the CS building at the University of Manchester, it's the size of a forearm and IIRC stored 1 byte :) * A CRT RAM thing. It's a refreshing RAM that takes advantage of the persistence of the the phosphor glow.
- jacquesm 8y ago"each Williams tube could typically store about 1024 to 2560 bits of data" From: https://en.wikipedia.org/wiki/Williams_tube https://en.wikipedia.org/wiki/Williams_tube
- monocasa 8y agoWilliams tubes don't rely on the phosphar coating (and some don't have a phosphar coating at all). It's all about the static electricity on the tube.
- bjackman 8y agoOh yeah, that's true. Thanks for correction.
- 0xdada 8y agoThey are mentioned in Turing's Cathedral [0], an excellent book that was recommended here on HN. Here's an interesting quote: There were two sources of noise: external noise, from stray electromagnetic fields; and internal noise, caused by leakage of electrons when reading from or writing to adjacent spots. External noise could, for the most part, be shielded against, and internal noise was controlled by monitoring the "read-around ratio" of individual tubes and trying to avoid running codes that revisited adjacent memory locations too frequently -- an unwelcome complication to programmers at the time. The Williams tubes were a lot like Julian Bigelow's old Austin. "They worked, but they were the devil to keep working" Bigelow said. This phenomenon is very similar to the recently discovered row hammer vulnerability of DRAM memory, except it predates it by roughly 65 years. [0] https://books.google.co.uk/books?id=dMK3P6B3WgcC https://books.google.co.uk/books?id=dMK3P6B3WgcC [1] https://en.wikipedia.org/wiki/Row_hammer https://en.wikipedia.org/wiki/Row_hammer
- greenyoda 8y agoThat's a wonderful story! The biography Alan Turing: The Enigma (which I highly recommend) also goes into a lot of detail about the early computers that Turing worked on: https://www.amazon.com/dp/069116472X https://www.amazon.com/dp/069116472X I learned about Turing Machines as a CS student a long time ago, and got the false impression that he was only involved in theoretical pursuits (theory of computation, algorithms for cryptography, etc.). It was only after reading this book that I learned how much he had contributed to the design of actual computing hardware. > trying to avoid running codes that revisited adjacent memory locations too frequently And today, it's exactly the opposite: we try to write code that has as much locality of reference as possible so that we can avoid expensive cache misses.