34C3 - The Ultimate Apollo Guidance Computer Talk

This is amazing to see - completely unpotted AGC! I've been following Curiousmarc's channel for a while and it's great to see this. Anyone interested in AGC stuff might also want to check out this video from the 34th Chaos Communication Congress that exhaustively explains how it works: [VIDEO]

This is awesome. If you haven't seen this talk about the AGC you should definitely check it out: [VIDEO]

For anyone interested in the AGC itself I can recommend the "ultimative Apollo guidance computer talk" [VIDEO]

This is the best description of AGC I have seen so far, from hardware design to mission software, layer by layer: "The Ultimate Apollo Guidance Computer Talk" [VIDEO]

If anyone wants to learn more about the Apollo Guidance Computer, this talk[1] from 34C3 will teach you everything you wanted to know and more. The AGC had some really fascinating features for the time, including a cooperative multitasking system, interrupt driven IO, and even a virtual machine for doing linear algebra! [1] [VIDEO]

Mandatory Light Years Ahead | The 1969 Apollo Guidance Computer [LINK] 34C3 - The Ultimate Apollo Guidance Computer Talk [VIDEO]

The best presentation I have seen on the AGC architecture: [VIDEO] It does present addresses in hexadecimal, oddly. The computer was 15-bit and used octal in its display panel. I suppose the presenters thought the audience would understand hex better.

> Aren't system designers at fault for coming up with the idea of a context switch Context switching was in the Apollo 11 guidance computer [VIDEO] The problem is that cycle-speed boosts left the industry cic. 2012-or-so. All the perf boost we get these days is by optimizing the instruction sequencing and multiprocessing. This is why languages like Go popped up (making the advanced programming topic of multiprogramming an entry-level accomplishment) and you now see the 'async' decorator plastered everywhere in C#, and so-on. Keeping the security context intact and separated is a gargantuan task. To me it makes more sense to add "lousy cores" to the die and force the operator to declare the launching threads are safe for SMT, else the job gets scheduled to the less-performing core where the pipelining is safer. It delegates responsibility to the chip-gobbler, forces them to understand the tradeoff for performance, until some elegant solution is found for side channel attacks like this.

For a comprehensive exposition of the technical aspects of the AGC, look no further than the Ultimate Apollo Guidance Computer Talk: [VIDEO] They not only do a brilliant job of exposing this niche system, but it is a foundational lecture for my knowledge of computer architecture in general

Michael’s blog is one of my favorites. His “Ultimate Guide” talks are great and I rewatch them at least once a year. Ultimate Guide to the C64: [LINK] Ultimate Guide to the Game Boy: [LINK] Ultimate Guide to the Apollo Guidance Computer: [VIDEO]