diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2021-11-28 09:50:00 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2021-11-28 10:44:40 -0800 |
commit | 6388bc08c46c096b3df91a5deddd2ac740cd6d38 (patch) | |
tree | 0d062e5b0c00fc6fa645ed3c5621564778c9947c /chesstv.tlv | |
parent | 13bfb7308a28d854c9a4685e99bf9d7ea2b2e20d (diff) | |
download | teliva-6388bc08c46c096b3df91a5deddd2ac740cd6d38.tar.gz |
save a snapshot of editor state across restarts
We're not using this yet. I agonized over this decision for several weeks. Is Teliva's need to restart with execve an utter hack or a good thing? I'm leaning towards the latter. Constantly exercising the initial flow makes Teliva more crash-only. We can build Steve Yegge's idea of immortality (http://steve-yegge.blogspot.com/2007/01/pinocchio-problem.html) out of crash-only primitives, just by making reboots instantaneous. But focusing directly on immortality tends to compromise crash-only by exercising it more rarely. One other issue this brings up: loading these Lua tables from disk is a vector for arbitrary code execution. I need to fix these when I get to sandboxing.
Diffstat (limited to 'chesstv.tlv')
0 files changed, 0 insertions, 0 deletions