|
|
|
@@ -25,10 +25,10 @@ a web of resilience which we'll end up building. |
|
|
|
## Priorities and tradeoffs |
|
|
|
|
|
|
|
It is very important for Collapse OS to be self-contained, that is, usable and |
|
|
|
hackable with no external ressources. Because of that, code simplicity is |
|
|
|
hackable with no external resources. Because of that, code simplicity is |
|
|
|
paramount. |
|
|
|
|
|
|
|
It is also important for Collapse OS to run on very tight ressources. Because of |
|
|
|
It is also important for Collapse OS to run on very tight resources. Because of |
|
|
|
that, code compactness trumps efficiency or features. |
|
|
|
|
|
|
|
All of this means that simplicity is more important than compactness which is |
|
|
|
@@ -41,7 +41,7 @@ course favor efficiency. |
|
|
|
|
|
|
|
This project is not made with irony. When being faced with existential threat, |
|
|
|
irony offers us a lot of comfort, but this project is not meant to supply this. |
|
|
|
It's self evident that this project is a rich source of possible ironic |
|
|
|
It's self-evident that this project is a rich source of possible ironic |
|
|
|
pleasure. To that end, I suggest a fork. Maybe call it "Pip Boy 3000"? |
|
|
|
|
|
|
|
## Roadmap rigidity |
|
|
|
|
overkill