>Its primary purpose is to be maximally useful during the first stage of civilizational collapse, that is, when we can't produce modern computers anymore but that there's still many modern computers around.<p>Any event or series of events that removes mankind's ability to produce modern computers is a global extinction-level event and rather than dicking around with computers one should really be considering suicide to avoid a slow, painful, inevitable death in a hostile world surrounded by misery.<p>People act like computers are complicated. They are but they also aren't.<p>Any moderately-sized US state university can (and some have) build one from scratch: as in from fucking sand to "Shall we play a game?", all in one go.<p>The state university nearest to me has a complete nanofab that can make-- and package!-- ICs (somewhere around 14nm-ish), a different lab that can make wafers from scratch, a chemistry department where undergrads could make the plastics, and all of the software guys you can shake a stick at.<p>The loss of the ability to make many things, including computers but also other more important things like the industrial process for making ammonia, globally, simultaneously, is the end of humanity.<p>The knowledge and ability is so widely globally distributed that taking it all out is death.<p>Do not mistake the centralization of consumer goods assembly with the centralization of the knowledge needed to assemble consumer goods.<p>Is this OS just for the brief period of time between the loss and the ultimate end? To like, play some rounds of solitaire while awaiting the inevitable?
There's a lot of idiosyncratic verbiage about stuff like collapse of civilization and users vs. operators, but it's not clear to me what makes this more lightweight or hackable than a typical lightweight RTOS or even just baremetal drivers running on a microcontroller.
I think many of us feel a lot of existential dread about the future these days, and if hacking on an OS helps the author cope with those feelings and improves their psychology, then I'm all for it. Whatever keeps you sane.
Seems like a wishful thinking about the first stage portion of collapse. You're going to be more interested in running some obsolete version of Windows that controls some proprietary infrastructure hardware, not running calculations of whatever kind or building things from scratch.
Recent issue of Wired has an interview with the author <a href="https://www.wired.com/story/forth-collapse-os-apocalypse-programming-language/" rel="nofollow">https://www.wired.com/story/forth-collapse-os-apocalypse-pro...</a>
Tbh I agree with <i>almost</i> every word there, but I can't believe this OS would be of any help in such a situation.<p>In dusk of our civilization it will not be possible to boot this OS from any modern computer. Those things nowadays don't even have CD. everything is dependent on internet, our data is being disowned by us and put into cloud. In case of broken internet the knowledge is going to be lost.<p>And how we're going to connect to this site using http? Via dialup?
Let me preface that I do not subscribe to the ideology at all, but the concept of bootstrapping a complex system is intellectually worthwhile and often practical in its use-cases. For example, imagine a tech company with a bunch of datacenters that boot from the network, have redundancy etc, but if you somehow turn the macthines off all at once, no one knows if they can reboot safely (say, service discovery cannot find the machine hosting OS images anymore).<p>As a practical matter, you can flip the author's mental pessimism and look at the optimistic situation where we conquer other planets, in which case thinking about an optimal bootstrapping path is going to be essential for the society and its industrial needs.<p>It is also true that some fairly local shocks in human society can cause a cascading failure and doing this analysis fairly regularly can help identify and minimize the cascade.
Related:<p><i>Collapse OS</i> - <a href="https://news.ycombinator.com/item?id=43482705">https://news.ycombinator.com/item?id=43482705</a> - March 2025 (199 comments)<p><i>Running CollapseOS on an Esp8266</i> - <a href="https://news.ycombinator.com/item?id=38645124">https://news.ycombinator.com/item?id=38645124</a> - Dec 2023 (1 comment)<p><i>Dusk OS: 32-bit Forth OS. Useful during first stage of civilizational collapse</i> - <a href="https://news.ycombinator.com/item?id=36751422">https://news.ycombinator.com/item?id=36751422</a> - July 2023 (141 comments)<p><i>DuskOS: Successor to CollapseOS</i> - <a href="https://news.ycombinator.com/item?id=36688676">https://news.ycombinator.com/item?id=36688676</a> - July 2023 (4 comments)<p><i>Collapse OS – Why?</i> - <a href="https://news.ycombinator.com/item?id=35672677">https://news.ycombinator.com/item?id=35672677</a> - April 2023 (1 comment)<p><i>Collapse OS: Winter is coming</i> - <a href="https://news.ycombinator.com/item?id=33207852">https://news.ycombinator.com/item?id=33207852</a> - Oct 2022 (2 comments)<p><i>Collapse OS</i> - <a href="https://news.ycombinator.com/item?id=31340518">https://news.ycombinator.com/item?id=31340518</a> - May 2022 (8 comments)<p><i>Collapse OS Status: Completed</i> - <a href="https://news.ycombinator.com/item?id=26922146">https://news.ycombinator.com/item?id=26922146</a> - April 2021 (2 comments)<p><i>Collapse OS – bootstrap post-collapse technology</i> - <a href="https://news.ycombinator.com/item?id=25910108">https://news.ycombinator.com/item?id=25910108</a> - Jan 2021 (116 comments)<p><i>Collapse OS Web Emulators</i> - <a href="https://news.ycombinator.com/item?id=24138496">https://news.ycombinator.com/item?id=24138496</a> - Aug 2020 (1 comment)<p><i>Collapse OS, an OS for When the Unthinkable Happens</i> - <a href="https://news.ycombinator.com/item?id=23535720">https://news.ycombinator.com/item?id=23535720</a> - June 2020 (2 comments)<p><i>Collapse OS</i> - <a href="https://news.ycombinator.com/item?id=23453575">https://news.ycombinator.com/item?id=23453575</a> - June 2020 (15 comments)<p><i>Collapse OS – Why Forth?</i> - <a href="https://news.ycombinator.com/item?id=23450287">https://news.ycombinator.com/item?id=23450287</a> - June 2020 (166 comments)<p><i>Collapse OS – Why?</i> - <a href="https://news.ycombinator.com/item?id=22901002">https://news.ycombinator.com/item?id=22901002</a> - April 2020 (3 comments)<p><i>'Collapse OS' Is an Open Source Operating System for the Post-Apocalypse</i> - <a href="https://news.ycombinator.com/item?id=21815588">https://news.ycombinator.com/item?id=21815588</a> - Dec 2019 (3 comments)<p><i>Collapse OS</i> - <a href="https://news.ycombinator.com/item?id=21182628">https://news.ycombinator.com/item?id=21182628</a> - Oct 2019 (303 comments)
I feel I can empathize with the ideology, and I want to argue that an idea like this is a big piece of some puzzle.<p>The puzzle: During the collapse, I think the biggest thing we would lose is our ability to communicate with each other in a reliable way. Like telecommunications and internet and all that. Who and what do we trust?<p>I imagine that before a collapse like this would happen, people would get a hint to gather as much as they can to help with their survival. Those things would include: this OS, the knowledge to load a sequence of bytes from whatever device is holding the OS to as many CPUs/controllers as possible, strategies to connect any number of arbitrary CPUs to radio devices, some knowledge of public keys and private keys. maybe all neatly organized into a handbook<p>The OS itself would be responsible for providing as easy an interface for any average joe to generate public/private keys, communicate with other people who have followed their same protocol, and use those public keys to build trust from communications. before the collapse happens, you may even collect a list of public keys you are likely to already trust.<p>The OS could maybe even have software for building communities of trust or even handling adhoc finances through (don't hate me for this) cryptocurrency.<p>anyways, this is all based on an assumption that the ability to communicate quickly (and build trust in a decentralized yet controllable way) is the best mitigation we have to a collapse<p>this answer is slightly influenced by the movie leave the world behind lol
I've seen this before, thought it was super interesting, kudos to the author. Leaving this comment for contrast with some other negative comments.
I think that in the event of a such a collapse, there would be two new directions: turning the surviving advanced digital devices into general computers, and building new electronics. Reusing existing common software would be easier than building something from scratch. So, I'd expect that postmarketOS and flavours of Linux for low-power machines meets most needs.<p>Also, it'd be fantastic if iPhones have a doomsday switch that untethers them from Apple - that'd be the difference between a useless brick and a precious artifact of a bygone era. The post-apocalyptic setting has potential for a game that comes from the perspective of a builder, and goes deeply into civil engineering and IT - build architecture that can withstand the elements, design a water chip, write embedded software for it.
I hope the author doesn't take this the wrong way, but this feels like another Temple OS driven by a different (perhaps milder) kind of insanity.<p>It's quite technically impressive, but I'm not sure I'd know what to do with it if I were experiencing an apocalypse, in a way that would be more useful to me than an install of Windows XP or Linux or Freedos would be
Many comments strawman the author then argue with what they imagine he images. Guys just read the 'Why' page [0] and argue with his thesis. I'm not sure to agree with everything but it still is a very interesting and questioning read. Kudos to the author for writing it.<p>This OS is <i>not</i> for:<p>- you or your child<p>- a planet with working computers<p>- a planet with cheap and abundant 'bootstrap' energy like we had from 1850 to 1960<p>- a planet where humans <i>really</i> struggle to get food ("you're running away from cannibals", but I think this metaphor is a bad choice after the mad-max refutation)<p>That page [1] is also a core part of the theory: "What makes collapse inevitable and imminent".<p>[0] <a href="https://collapseos.org/why.html" rel="nofollow">https://collapseos.org/why.html</a>
[1] <a href="https://collapseos.org/civ.html" rel="nofollow">https://collapseos.org/civ.html</a>
> <a href="https://git.sr.ht/~vdupras/duskos/tree/master/item/fs/io/kbd.fs" rel="nofollow">https://git.sr.ht/~vdupras/duskos/tree/master/item/fs/io/kbd...</a><p>I don't know forth. Is this a driver? How does it talk to the hardware?
I think forth is fun, but I can't really take the collapse narrative of this project seriously. IG it's disrespectful, but I kinda view it as a performance art piece with fallout vibes.
Whenever I see something like this I wonder: how is it more valuable than porting freeDOS/busybox to the same environments, with its dearth of existing software and hardware support
That "civilizational collapse" scenario must be straight out of the Fallout game.<p>In my mind I was reading their page with the voice of Ron Perlman - "FAT, FAT never changes...".
Where can I go to learn how to scavenge for microcontrollers and load/operate an OS like this on them? (Low-key would like to know that I could do that if need be).
According to the "Linking to this website" section:<p><pre><code> If you want to link to this website, please use http:// links rather than https:// ones. While http:// links are trivially "upgradable" to HTTPS, the opposite is not.
</code></pre>
Mods should update the link in this post