Philosophy
Essays on why libxtc is shaped the way it is.
---Essays on why libxtc is shaped the way it is:
- Why libxtc exists – the problem it solves and the shape of the answer.
- Choices and roads not taken – the alternatives that were considered and deliberately rejected, with the reasoning.
- Let it crash – why assuming success and recovering at a higher level beats defending against every error.
- Message passing and the compromise – pure shared-nothing versus the compromise libxtc strikes, and why that is the reason xtc and tnt both exist.
- Influences and lineage – the runtimes libxtc learned from (BEAM, Seastar, Tokio, Cats Effect, Scala Native), what it took from each, and the lines it deliberately did not cross.