Apollo-11 VS Atom

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

For JavaScript, HTML, and CSS, Visual Studio Code is the best solution because it already runs on the Electron framework. So, try VSCode. Don't worry; your device won't be harmed. If its performance was unbearable, you can always put it aside. You can also try Atom. It is outdated, but it could be answer to your need.

you can still get atom from it github page: https://github.com/atom/atom/releases/tag/v1.60.0

I'm surprised that nobody here mentioned Atom [1]. IIUC, Atom was designed to be hackable like Emacs.

A successor to Atom is Pulsar [2].

[1] https://github.com/atom/atom

[2] https://pulsar-edit.dev/

atom (RIP buddy! Free) Atom is a hackable text editor for the 21st century, built on Electron, and based on everything we love about our favourite editors. We designed it to be deeply customizable, but still approachable using the default configuration

Hey everyone, I'm developing an open source text editor called Valence. I'm just getting started with its development and the next and main thing I need to implement is the editor itself. Now I know there are many different code editors like CodeMirror, Ace.js and Monaco but I want to start from scratch and build something like Atom had done. Currently I created a contenteditable div and also added a custom cursor. BTW I'm using React, TailwindCSS and TypeScript. Here is the component

These versions of Atom will stop working on February 2 [2023]. To keep using Atom, users will need to download a previous Atom version.

For Mac users - mv ~/.atom ~/atom_bak rm -fr /Applications/Atom.app download https://github.com/atom/atom/releases/tag/v1.60.0 Drag download to Applications folder - to install

And it doesn't match because https://github.com/atom/atom/releases/download/v1.63.1/atom-amd64.deb returns a 404 not found error, so of course it doesn't match.