Tuna-i3-Plus VS Apollo-11

Other than the fact that 1, 2, and 3 are perfectly representable as integers in IEEE-754, there are a number of languages that have fixed-point types, C and C++ offer specific forms as compiler extensions, and it really isn't hard to implement in C++ using a templated class (though you get better ABI semantics for it in Clang with [[trivial_abi]]). Here's a crude implementation in C++17 for AVR, complete with mismatched tabs/spaces.

I did some similar things with my old libtuna for AVR, mainly with intsz and with how fixed-point values are handled.

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...