Collapse OS — Why?

I expect our global supply chain to collapse before we reach 2030. With this collapse, we won't be able to produce most of our electronics because their production depends on a very complex supply chain that we won't be able to achieve again for decades (ever?).

The fast rate of progress we've seen since the advent of electronics happened in very specific conditions that won't be there post-collapse, so we can't hope to be able to bootstrap new electronic technology as fast as we did without a good "starter kit" to help us do so.

Electronics yield enormous power, a power that will give significant advantages to communities that manage to continue mastering it. This will usher a new age of scavenger electronics: parts can't be manufactured any more, but we have billions of parts lying around. Those who can manage to create new designs from those parts with low-tech tools will be very powerful.

Among these scavenged parts are microcontrollers, which are especially powerful but need complex tools (often computers) to program them. Computers, after a few decades, will break down beyond repair and we won't be able to program microcontrollers any more.

To avoid this fate, we need to have a system that can be designed from scavenged parts and program microcontrollers. We also need the generation of engineers that will follow us to be able to create new designs instead of inheriting a legacy of machines that they can't recreate and barely maintain.

This is where Collapse OS comes in.

There are two stages of collapse

(Disclaimer before I'm called a nutjob over this: I'm not 100% certain that collapse is inevitable and imminent. I'm acting on a "strong hunch". That hunch is strong enough for me to think that time investment in this project, considering the possible rewards for humanity, is worth it.)

With regards to this project, there are two important stages of collapse. The first one is when the global supply chain is broken and the second one is when, in a particular community, the last modern computer dies.

There are decades between the two. Sure, modern technology is generally fragile and unfixable, but there are many robust modern computers hardware and those that are lucky enough to run a self-contained operating system will continue to provide a modern computing environment for decades.

Therefore, you and I are likely to be dead before Collapse OS is actually useful. However, communities with good foresight will immediately start to work on creating post-collapse computers because a lot of work will have to be poured on their own local copy of it before it runs smoothly on the hardware they manage to scavenge and retrofit. They also have to become proficient in maintaining it. Their children also have to.

That's the perspective we have to keep in mind in this project. Collapse OS doesn't have to run smoothly, but it has to be easy to grok in its entirety and, most importantly, gather vital knowledge about as many components as possible in one self-contained place.

Open questions

Futile?

This project is only relevant if the collapse is of a specific magnitude. A weak-enough collapse and it's useless (just a few fabs that close down, a few wars here and there, hunger, disease, but people are nevertheless able to maintain current technology levels). A big enough collapse and it's even more useless (who needs microcontrollers when you're running away from cannibals).

But if the collapse magnitude is right, then this project will change the course of our history, which makes it worth trying.

This idea is also fragile because it might not be feasible. It's difficult to predict post-collapse conditions, so the "self-contained" part might fail and prove useless to many post-collapse communities.

But nevertheless, this idea seems too powerful to not try it. And even if it proves futile, it's a lot of fun to try.

32-bit? 16-bit?

Why go as far as 8-bit machines? There are some 32-bit ARM chips around that are protoboard-friendly.

First, because I think there are more scavenge-friendly 8-bit chips around than scavenge-friendly 16-bit or 32-bit chips.

Second, because those chips will be easier to replicate in a post-collapse fab. The z80 has 9000 transistors. 9000! Compared to the millions we have in any modern CPU, that's nothing! If the first chips we're able to create post-collapse have a low transistor count, we might as well design a system that works well on simpler chips.

That being said, nothing stops the project from including the capability of programming an ARM or RISC-V chip.

What is scavenge-friendly?

By "scavenge-friendly electronic parts", I mean parts that can be assembled with low-tech tools. I mostly mean parts with a "through hole" mounting type (in opposition with "surface mount").

"But I do tons of hobbyist electronics with surface mount!", some could say. Yeah, sure, but how do you wire it? You order a PCB from OSH Park? That's not very scavenge-friendly.

One solution could be breakout boards, but if your ability to use a surface mount chip is limited by the availability of breakout boards of a type that matches your chip, then it severly limits your likeliness of finding a usable chip in your scavenging operations.

"But you still need protoboards with through hole!", some could say. In a sense, yes, wiring is much easier with protoboards, but you could still manage to cobble up something together with a hand-perforated board. Also, protoboards are reusable. If you have a limited supply of them, you can still desolder an old design and reuse the protoboard in a new one. So, a post-collapse community with a limited supply of protoboards can still achieve a lot.

Some modern CPUs are available in through hole packages, but because surface mount is so much more popular, in modern electronics, than through hole, you are very unlikely to stumble upon one of those chips in scavenging operations. Hence, "I think there are more scavenge-friendly 8-bit chips around than 16-bits or 32-bits ones".

Prior art

I've spent some time doing software archeology and see if something that was already made could be used. I found no open source program that self-hosted on Collapse OS' target machine.

A close contender is CP/M. It recently had its source code made available, but unfortunately not under a proper open source license. There's a ticket on github evaluating CP/M's suitability to Collapse OS' goals in more details.

Then comes the idea of piggy-backing from an existing BASIC interpreter and make a shell out of it. Interesting idea, and using Grant Searle's modified nascom basic would be a good starting point, but I see two problems with this. First, the interpreter is already 8k. That's a lot. Second, it's copyright-ladden (by Searle *and* Microsoft) and can't be licensed as open source.

Nah, maybe I worked needlessly, but I preferred starting from scratch.

On what basis do you believe that a collapse of the global supply chain is probable by 2030?

First of all, this is a belief, not knowledge. Science cannot prove that we are likely to collapse. Science cannot prove that we are unlikely to collapse.

What made me turn to the "yup, we're fucked" camp was "Comment tout peut s'effondrer" by Pablo Servigne, Éditions du Seuil, 2015. It's not perfect, but is a very good introductory book, well written, pleasing to read (except for the existential sinking feeling). For french-impaired fellows, the book has recently been translated to English. Then, from that read, you simply tumble down the rabbit's nest.

That being said, I don't consider it unreasonable to not believe that collapse is likely to happen by 2030, so please, don't feel attacked by my beliefs.

Electronics evolved rapidly without any help before. Why can't we pull it again?

These technological breakthroughs happened in a context of cheap energy. Unless we have a "unicorn tech" (nuclear fusion for example) giving us cheaper energy than 1960's oil, we will never again see these days of extraordinarily cheap energy.

Without cheap energy, we have less energy to divert to scientific advancement, so we stagnate. After a collapse, most of our infrastructure will be destroyed or unusable. The investment needed to get a proper infrastructure back on its feet will be impossible to make without cheap energy, so we won't.

This is why low-tech is so important, because low-tech is compatible with a context where energy is expensive.

Of course, if you believe in unicorn technology, then Collapse OS, and low-tech in general, is futile. Yet again, a matter of belief. I never believed in unicorns.

Aren't there more important things to do than an operating system?

Yes! Yes! Yes! A metric ton of projects are more important than Collapse OS with regards to civilizational collapse. This doesn't make Collapse OS useless.

I created Collapse OS because I think that I have a very specific combination of knowledge and skills that allow me to fill this niche with a minimal time investment.

Some people say "When collapse comes, you'll be way too busy with survival to spend time with Collapse OS". When you look at survival from an individualistic point of view (which is the point of view of the stereotypical "prepper"), that is very true. Don't waste time with Collapse OS.

However, when you look at it from a communal perspective, Collapse OS starts to make sense. Once a particular community already took care of its immediate survival and is looking at going from "surviving" to "thriving", if it has Collapse OS and someone who can make sense of it, then that community will have a great asset.