4 ms·
I can't recommend "The Apollo Guidance Computer: Architecture and Operation" book highly enough. It's an awesome book that looks into details of AGC's inner wo
by cyberax 3y ago
I can't recommend "The Apollo Guidance Computer: Architecture and Operation" book highly enough. It's an awesome book that looks into details of AGC's inner workings.
One interesting tidbit: the raw machine code in AGC was a veritable Turing Tarpit-style hell. So instead of just powering through it, they added an interpreter for a much more human-friendly language that ran on top of it.
Levels of abstraction: they're not just for enterprise applications!
- wibbily 3y ago"Digital Apollo" by David Mindell is also excellent. It covers the development of the AGC and other flight computers at the Instrumentation Lab, and puts a lot of the design details of the AGC in context.
- KineticLensman 3y agoAgree with this recommendation. There's also a lot on the related 'cultural' aspects as the designs evolved, e.g. pilots vs. mission control in terms of who has primacy, who has the best instrumentation, etc.
- djmips 3y agoOf course levels of abstraction aren't just for enterprise applications - any non trivial assembly language program introduces some level of abstraction. The VM was a clever idea, especially for the sixties in such a compact machine. I used to use Sweet16 by Woz in the early eighties and used in in a similar manner adding to the instruction table to give me high level disk drive commands for example. https://en.wikipedia.org/wiki/SWEET16 https://en.wikipedia.org/wiki/SWEET16 I found some of the interpreted commands for Apollo 11 here https://www.ibiblio.org/apollo/Documents/HSI-208472.pdf https://www.ibiblio.org/apollo/Documents/HSI-208472.pdf
- maxbond 3y agoIndeed, abstraction goes all the way down, and electrical components like resistors, capacitors, and transistors are abstractions. The components themselves are largely different configurations of the similar materials and subject to the same forces. Eg, every resistor is to some degree a capacitor, and an LED, a transistor, and a solar panel are all variations on the same technology (and you can usually abuse them to fulfill one of the other roles). The distinctions are a structure we impose to create an environment friendly to engineering - abstractions.
- MichaelZuo 3y agoEven machine code itself is an abstraction, especially on x86, where the actual micro-code that the physical circuits would recognize is different.
- djmips 3y agoIt is fascinating to read over the details of that abstraction. I hadn't realized the x86 was micro-code from day 1. https://www.righto.com/2022/11/how-8086-processors-microcode-engine.html https://www.righto.com/2022/11/how-8086-processors-microcode...
- whateveracct 3y agoSoftware development was better back then. You'd never be allowed to do that today.
- deaddodo 3y agoA good chunk of code being written today is machine microcode that's been abstracted into opcode then abstracted into an OS that runs code written in C/C++ compiled into an executable pretending to be another machine which executes its own bytecode interpreted from JavaScript code that was transpiled from TypeScript. Not sure how many more levels of abstraction you'd want.
- whateveracct 3y agoYou know modern software is bad when abstraction has lost its meaning and become a bad word.
- deaddodo 3y agoThe way you worded this, I'm not sure if you're attacking my point or corroborating it. It sounded like you appreciated that the AGC simplified things via abstraction and then implied it wasn't possible to do today, despite that being the basis of all modern tech. I wasn't attacking abstraction in any way.
- DylanSp 3y agoSunburst and Luminary [1] mentioned using the native LGC assembly for some performance-sensitive parts of the flight; do you know how common that was/how much of the code was written that way? [1] https://www.amazon.com/Sunburst-Luminary-Apollo-Don-Eyles/dp/0986385905 https://www.amazon.com/Sunburst-Luminary-Apollo-Don-Eyles/dp...