Follow

Collapse OS:
- Run on minimal and improvised machines.
- Interface through improvised means (serial, keyboard, display).
- Edit text files.
- Compile assembler source files for a wide range of MCUs and CPUs.
- Read and write from a wide range of storage devices.
- Replicate itself.

collapseos.org/

LB 

@yaaps @yogthos @dirtycommo I'm reading along now.

On one hand, I hope they are wrong. On the other hand, I'm glad someone is preparing.

LB 

@dirtycommo @yogthos @ajroach42
I think the decline in the use of 16 bit microcontrollers in the last 10 years and the paucity of efficient 16 bit designs would probably be an issue an issue if semiconductor technology was restarting by replicating 8 bit designs. A 16 bit CISC design like the 8088 has nearly as many transistors (29k) as a 32 bit RISC design (A6, 35k), so developing 16 bit computing could be a hiccup in recovery unless effort is made to ensure a viable technology is documented. This might be a start...

user.eng.umd.edu/~blj/RiSC/

@yogthos on the one hand I'm pretty sure if civilization collapses, getting a basic computer to work with spare parts would be the last of your worries.

On the other hand this project is far too much fun for me to dismiss for rational reasons. :blobowo:

@polychrome @yogthos

If I were going to build something like this, I'd probably go with something in the neighborhood of Forth. An interactive building-block language whose bottom layer can bang on hardware but also provides high-level features written in itself.

So something that you can keep building on as long as you have resources but will work at whatever level you stop at.

@polychrome @yogthos

So anyway, I now have an org-mode file full of notes on how to do low-memory Lispish stuff without garbage collection or a clever allocator.

@polychrome @yogthos That's been my experience. When the shit hits the fan, and you are worried about food, shelter, and water, that's all you have time or energy to think about. Add to that the likelihood of massive civil unrest, violence, and such, and I doubt anyone will have time to fuck with computers.

@bamfic @yogthos @polychrome Then again, wouldn't it be nice to be able to have a little computer to help with organizing? Or do math and stuff?

@bamfic @yogthos @polychrome

Eg. try watching a few old episodes of the BBC's computer education stuff. It's from an era where personal computers were just beginning to become popular and it's very interesting to hear the stories of how computerization gave businesses an edge.

My theory is that even if we went full Fallout-style-post-apocalyptic, the communities that could maintain their communication infrastructure and use computers to plan and optimize workflows would have an edge over those who don't.

@bamfic @yogthos @polychrome

Other example: inventory management

if scarcity becomes a problem, it would be very helpful to know what resources your community has

@yogthos

I'm pretty sure there will be an ample supply of >386 hardware available to run Linux on.

@yogthos

I think what bothers me is that it's retro for its own sake. If we were forced to go back to 1980-era hardware, it would still be more advanced than it was then because we've learned a lot more about software and HCI.

We understand the power of high-level languages these days in a way they didn't really grok back then.

@yogthos It's about time someone started coding with apocalypse tolerance in mind.

@yogthos My only concern with this project is the requirement for 56K of RAM. This is an obscene amount of memory to expect to find when scavenging. It also complicates address decoding, which means a harder to build computer.

I would have preferred to see 16KB or 32KB being the basis configuration, something where a single NAND gate can form the basis of an address decoder. (This is how I built my Kestrel-1 SBC prototype, for example.)

@yogthos a simple computer that anyone can program would be very useful in a post-whatever scenario.

I mean, it would be useful now.

I think the most important thing is that it needs to be simple enough that anyone can easily learn how to utilize all of it's capability. This was common in early personal computers.

Not saying we can't improve using what we've learned since then, but I think it's very easy to underestimate the value of simplicity and accessibility by rationalizing the use of "modern" computing techniques.

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!