HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
chrislgarry
Apollo-11
Assembly2016–2026
chrislgarry / Apollo-11

Apollo-11

Original Apollo 11 Guidance Computer (AGC) source code for the command and lunar modules.

100Distinct people
111Mentions
5Explicit recommenders
76.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Original Apollo 11 Guidance Computer (AGC) source code for the command and lunar modules.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

As immortalized by my favorite case[0] from the codeless code (based on real code [1] from Apollo 11). [0] http://thecodelesscode.com/case/234 [1]…

voiceblue used a recommendation phrase. 5 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 10:50:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year111 dated mentions

Observed mentions: 2016-07-05 16:22:14 UTC to 2026-10-08 15:49:53 UTC.

01020302016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 26 mentions; 5 submissions, 21 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 12 mentions; 3 submissions, 9 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 17 mentions; 7 submissions, 10 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 10 mentions; 4 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 6 mentions; 4 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 12 mentions; 4 submissions, 8 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC26521
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC633
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1239
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC17710
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC615
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC321
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC725
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC606
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC1046
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC642
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC1248

What Hacker News says

17 sources
Bit strange thinking of Python as "old" .. anyway, what I suspect happened was that tabs were the "new" innovation - in the post-punchcard era. Punchcards couldn't meaningfully have a tab character, but they could have fixed character positions, and this feature was required by COBOL and FORTRAN in their day. It was still present in the F77 standard. I think the other thing that got in the way of standardising on TAB was that 8 character indent is too much, but once you let people configure it it's no longer consistent between systems. > that's some impressively old code to find on GitHub You may like https://github.com/chrislgarry/Apollo-11
In A Mystery of Unix History
The detailed and verbose comments are amazing. Not to mention I have zero idea what the assembly code or even the math is doing. from https://github.com/chrislgarry/Apollo-11/blob/master/Luminar... # SINCE WE WILL FIND THE MODE 1 SHAFT ANGLE LATER, WE CAN FIND THE MODE 1 TRUNNION BY SIMPLY TAKING THE ARCSIN OF THE Y COMPONENT, THE ASIN GIVIN AN ANSWER WHOSE ABS VAL IS LESS THAN 90 DEG. Nervously looks around.. Ummmm what?
In The (Surprisingly Funny) Code for the Apollo Moon Landings Is on GitHub
It's funny that the personified user interface is used as the title, because the star of the show is something much more hidden - one of the first multitasking "operating systems" correctly handling, and limiting the impact of, an unforeseen CPU-hungry process in the midst of the first moon landing! The OP's a fascinating read and more technical than the title might imply. For anyone interested in the process of compiling and loading the code for these systems (available at https://github.com/chrislgarry/Apollo-11/ ) into the "core rope memory" used for program storage in the capsules, here's one of the original spec documents, as well as an image from that document showing what I'd call a "compilation-bureaucracy-pipeline" that's a fascinating glimpse into software deployment practices. https://www.ibiblio.org/apollo/Documents/HSI-208496
Read the rest
In Diskee: Apollo's Most Important Crewmember

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.