2 ms·
I think that's right. The ENIAC people were working on ballistics for large guns, and needed to crunch numbers and create printed tables. The Turing team was w
by Animats 1y ago
I think that's right. The ENIAC people were working on ballistics for large guns, and needed to crunch numbers and create printed tables.
The Turing team was working on key-testing, like a Bitcoin miner. Colossus was a key tester, trying patterns zipping by on endless loops of tape, and recording matches. Any general purpose machine today can do both, but the early machines were specialized.
What general purpose architecture should roughly look like was known all the way back to Babbage. Some kind of long list of instructions, with unconditional and conditional branches. Zuse and Atanasoff both got there before WWII.
The big hangup was memory. All early computing struggled with memory limitations, as I mention occasionally. CPUs and instruction decoding came long before enough memory to store programs. Memory was still a million dollars a megabyte in the mid-1970s.
- vlovich123 1y agoNo general purpose compute was not known during Babbage’s time. He happened to have been in the process of building a Turing complete machine, but that’s largely accidental - he didn’t understand why it could do so many things and it wasn’t until the work of Hilbert, Gödel, Turing and Church that the picture really came into focus and these machines really started to get built consistently and reliably with a key understanding of what features the machine needed to have. Z3 wasn’t Turing complete and z4 can’t start Turing’s work