I would have thought the major problem after a technological collapse would be the production of computer hardware, even up to the level of something like ENIAC, as the technology stack needed to create that represents centuries of technological development.
Software development, on the other hand, took merely decades, and would be much faster to reboot, as computer language and compiler technology can be easily reinvented given information in printed books. If anything, I'd suggest an emphasis on having paper copies of books on classic programming languages and computer history widely distributed in paper libraries, and making sure that paper libraries are not displaced entirely by electronic ones.
I'd consider archiving full documentation of pre-existing basic technology, rather than rolling your own; a widely distributed complete set of printed books, circuit diagrams, manuals, source code and assembly code listings capable of reproducing something like BCPL on PDP-11 might be a better choice; creating something like a PDP-11 class computer with valves or relays would be eminently feasible.
The main idea, with Collapse OS at least, is to be able to build software with salvaged computer parts. The focus is on easy to repair chipsets, that could be maintained with access to simple tools.
I hope that a decade or two down the line with cheap solar and batteries, we become less dependent on a grid for business as usual and for rebooting after local or widespread collapse.
Societies has bee surprising resilient to large scale disruption in the past...
Solar power of course, the problem is: who will manufacture new chips for our salvaged computers?
A specialized civilization like ours has a small window to reboot before tech degrades and scavenging becomes harder. After that short window, securing food, shelter and defense would be the primary goals.
I still really like the idea of Collapse OS. I've loved computers all my life, and if bandits are going to raze my precarious settlement, I want to leave this mortal coil with a retro microprocessor in my arms.
I have a rather tricky time reading the guest language syntax. Is there a good reason you didn't use "normal" dot+parens method call syntax? Can you do more with yours?
Software development, on the other hand, took merely decades, and would be much faster to reboot, as computer language and compiler technology can be easily reinvented given information in printed books. If anything, I'd suggest an emphasis on having paper copies of books on classic programming languages and computer history widely distributed in paper libraries, and making sure that paper libraries are not displaced entirely by electronic ones.
I'd consider archiving full documentation of pre-existing basic technology, rather than rolling your own; a widely distributed complete set of printed books, circuit diagrams, manuals, source code and assembly code listings capable of reproducing something like BCPL on PDP-11 might be a better choice; creating something like a PDP-11 class computer with valves or relays would be eminently feasible.