Post Apocalypse Coding

The usual way of programming makes use of the programming ecosystem, which provides libraries and other code you can depend upon when writing your application. But what if this ecosystem suddenly does not exist anymore, what happens when you are left on your own with just the programming language itself?

The challenge is to pretend there are no third-party libraries for the programming language your are currently working in, as if an apocalypse happend and this infrastructure is no longer available. To help yourself build projects reasonably, you will also form primitive versions of common libraries and re-establish the classical ecosystems slowly.

It can also be taken a step further, considering that the only computer left is a more primitive one, and building low-level tooling up to an interpreter. That would be hard mode, and would be a proper apocalypse.

But even in a world where an apocalypse has not (yet) happend, it might be a good idea to think about the dependencies you have and how resiliant your software is to outside chaos. For instance, it might lead to vendoring or version pinning dependencies, and using the packages feature of your favorite git forge. The package system also supports a ton of specific repository-types, and it allowed me to also make the MBLF-packages available for download.