newsletters:2025-02
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| newsletters:2025-02 [2025/02/28 21:25] – osnr | newsletters:2025-02 [2025/03/31 12:18] (current) – [What we'll be up to in February] osnr | ||
|---|---|---|---|
| Line 43: | Line 43: | ||
| === Snapshots / state-saving / program-saving === | === Snapshots / state-saving / program-saving === | ||
| + | >> Is there a way to Hold something on disk so a page has permanent information? | ||
| + | >> Or is snapshotting the goal? | ||
| + | > | ||
| + | > we don't have this right now but i think it would be great to have | ||
| + | > | ||
| + | > 1. subsume awkward hacks where we use files in ad-hoc ways for persistence (.folk, .meta.folk, calibration) | ||
| + | > | ||
| + | > 2. crash resilience (your editor state can get preserved across crashes, etc) | ||
| + | > | ||
| + | > i think of snapshotting as a way to preserve/ | ||
| + | |||
| + | (snapshotting being "where you have virtual thumbnails on the printed page to represent all the programs, so they' | ||
| + | the thumbnail regions could all be captured from table session when the snapshot is taken (& shrunk down to fit on page), or i guess they could just be a grid if you have a statement that is just a straight list of program numbers like you propose?" | ||
| + | >> Could you have a separate process that journals the holds and writes to disk on crash or quit? | ||
| === Intercept discussion === | === Intercept discussion === | ||
| Line 167: | Line 181: | ||
| + | Notice the blinking of the editor -- this is extreme (other slow stuff is happening on the table), but it happens occasionally even while just normally typing/ | ||
| + | |||
| + | {{newsletters: | ||
| + | |||
| + | Tracy view when I type a bunch of stuff (see the blips on the keyboard thread for when I'm pressing keys) and the editor blinks out (see the dips on the plot at the bottom): | ||
| + | |||
| + | {{newsletters: | ||
| + | |||
| + | I did optimize the editor a bit by [[https:// | ||
| === Rob's test === | === Rob's test === | ||
| Line 178: | Line 201: | ||
| === Shared immutable (immortal) objects === | === Shared immutable (immortal) objects === | ||
| - | Omar: Mason and I spent a while throwing around ideas in Discord about how to share objects between threads (separate Jim interpreters) in folk2 without copying/ | + | Omar: Mason and I spent a while throwing around ideas in Discord about how to share objects between threads (separate Jim interpreters) in folk2 without copying/ |
| (' | (' | ||
| - | I think we have an OK plan for this, actually, and I [[https:// | + | I think we have an OK plan for this, actually, and I [[https:// |
| ==== Friends and outreach ==== | ==== Friends and outreach ==== | ||
| Line 245: | Line 268: | ||
| * Folk plugin for Procession that tells the LLM how to input/ | * Folk plugin for Procession that tells the LLM how to input/ | ||
| - | ===== What we'll be up to in February | + | ===== What we'll be up to in March ===== |
| * **Our next Folk open house is [[https:// | * **Our next Folk open house is [[https:// | ||
| Line 271: | Line 294: | ||
| ==== Andrés ==== | ==== Andrés ==== | ||
| - | * | + | * [[https:// |
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
newsletters/2025-02.1740777957.txt.gz · Last modified: by osnr
