Apollo-11 VS quine-relay

I often like to think about https://github.com/chrislgarry/Apollo-11 as an analogy. It's public domain with available source, in the assembly language in which it was written... so it fills all the definitions of OSS!

But the process by which that code arose, the ability to modify any line and understand its impact (heh) on a real execution environment, is dependent on a massive process that required billions of dollars and thousands of the smartest people on the planet. For all intents and purposes, without that environment, it is as reliably modifiable as an executable binary in any other context - or a set of weights, in this one!

But can a Transformer run on the Apollo Guidance Computer?

https://en.wikipedia.org/wiki/Apollo_Guidance_Computer

Frequency 2.048 MHz

Memory 15-bit wordlength + 1-bit parity

2048 words RAM (magnetic-core memory)

https://github.com/chrislgarry/Apollo-11/blob/master/Luminar...

You can look at the Colossus 2A code written by Margaret Hamilton and her very small team on Github.

"Burn Baby Burn" might be even more apt!

https://github.com/chrislgarry/Apollo-11/blob/master/Luminar...

My more positive take on this: our runtime environments are bloated because we have ways to enable trust, stability, and iteration speeds that people wouldn't have dreamed of in years past.

Your Notion desktop app and Google Chrome both support embedding & displaying multimedia content that's controlled by people that you may not trust, but they can draw on decades of engineering to sandbox that content. They can independently be updated without worrying about a centralized `flexbox.dll` that may or may not be the right version. They do not require building a new executable to make the vast majority of UI changes. And the cost is simply storage space and initial download bandwidth.

We can look with rose-colored glasses at an era of "every byte of assembly has been hand-crafted." I, too, look in awe at what was achieved with such things as https://github.com/chrislgarry/Apollo-11/tree/master/Luminar... . But that software, per https://en.wikipedia.org/wiki/Apollo_Guidance_Computer#Softw..., took 1400 person-years of work.

We have to compare apples to apples - the abstractions we have today would not prevent such a piece of software from being built, and indeed would allow us to build that exact software, even bit-for-bit the same, much more easily due to abstractions on our tooling itself. We have not departed a world where, given a nation-state budget, one could pay for 1400 person-years of work and create the AGC (though one might make arguments about the distraction levels of modern society, but that's a different thing entirely).

But we also exist in a world where I can build and ship a cross-platform video chat application in an afternoon (well, not counting app store approvals) and be reasonably confident that my app will be compatible with, and secure on, practically any computer or mobile device sold in the past half decade, regardless of how many other apps may have been installed on each device. I'd venture to say that Apollo engineers would, and do, find this aspect of our world fascinating, too.

Thankfully it was eventually migrated to GitHub

If there were more languages, then it'd be `console.log("System.out.println({python_source})")`, etc. The problem then becomes quoting and escaping inner quotes. I managed to avoid the problem by using both single and double quotes, and relying on Python's `repr` also giving valid JS strings, but if I had to add one more language I'd have problems.

I still think the Quine Relay is a tour de force, but for different reasons. It's not 128 quines in different languages, but an incredibly robust system for quoting and escaping strings in 128 different languages.

[1] https://github.com/mame/quine-relay/blob/master/src/code-gen...

One of the most impressive works I've seen: https://github.com/mame/quine-relay

"Quine" is a type of program, when executed, will output itself (it's actually it's source code). It's very hard to write one. And this guy wrote a loop quine. It supposed to work like this: * A program in language A output a program in language B * The program in language B output a program in language C * The program in language C output the same program in language A which we started with

Or a Quine relay.

Why use a couple of languages, when you can use 128 of them simultaneously? https://github.com/mame/quine-relay

Quine relay [1] is to this day the most "I will never understand this" brainfuck project I have ever seen.

[1] https://github.com/mame/quine-relay

Go look at a programming quine and tell me it isn't art.