User Tools

Site Tools


newsletters:2025-02

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
newsletters:2025-02 [2025/02/28 21:25] osnrnewsletters: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/version programs and persistent Hold as a way to preserve data i guess, i don't know if that distinction makes sense but that's how it is in my head
 +
 +(snapshotting being "where you have virtual thumbnails on the printed page to represent all the programs, so they're still pointable & have regions etc… 
 +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/backspacing:
 +
 +{{newsletters:img_7894.mp4?300px}}
 +
 +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:263550d2-1c28-4792-9e18-60b3d280c982-6265-0000034beb6ac656.png?450px}}
 +
 +I did optimize the editor a bit by [[https://github.com/FolkComputer/folk/commit/a88d925f541efde46169e55ad9828620232d5f5f|decoupling cursor state from rendering]], so it only blinks when you actually edit the code, not when you're moving the cursor. (It's cool how just by separating your logic into different independent Whens, your program feels like it gets more and more parallel and reliable...)
  
 === 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/reparsing.+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/reparsing (which is what both folk1 and folk2 do now, although it's a more acute problem in folk2 because stuff comes fresh out of the DB for every When execution)
  
 ('immortal' is [[https://peps.python.org/pep-0683/|a term from Python]] for what I think is a similar concept) ('immortal' is [[https://peps.python.org/pep-0683/|a term from Python]] for what I think is a similar concept)
  
-I think we have an OK plan for this, actually, and I [[https://github.com/FolkComputer/folk/tree/osnr/folk2-transients|started hacking on it]], but haven't really fully implemented it yet. Something to keep in pocket if we need it, maybe.+I think we have an OK plan for this, actually, and I [[https://github.com/FolkComputer/folk/tree/osnr/folk2-transients|started hacking on it]], but haven't really fully implemented it yet. Something to keep in pocket if we need it, maybe. (for now, the aggressive per-thread object cache mitigates the copying and reparsing a lot)
 ==== Friends and outreach ==== ==== Friends and outreach ====
  
Line 245: Line 268:
       * Folk plugin for Procession that tells the LLM how to input/output stuff       * Folk plugin for Procession that tells the LLM how to input/output stuff
  
-===== What we'll be up to in February =====+===== What we'll be up to in March =====
  
   * **Our next Folk open house is [[https://partiful.com/e/8zlZKFFAvyeFbngr9PUe|in the evening on Wednesday, March 26]], at our studio in East Williamsburg, Brooklyn.**   * **Our next Folk open house is [[https://partiful.com/e/8zlZKFFAvyeFbngr9PUe|in the evening on Wednesday, March 26]], at our studio in East Williamsburg, Brooklyn.**
Line 271: Line 294:
  
 ==== Andrés ==== ==== Andrés ====
-  * +  * [[https://www.instagram.com/reel/DFdi2U9tgEA/|Liquid paper sculptures]] 
 +  * [[https://endtimes.dev/why-you-should-dither-images/|Why Your Website Should Use Dithered Images]] 
 +  * [[https://www.greendesign.io/dithering-images|Dither images]] 
 +  * [[https://x.com/kevintwohy/status/1867964091769430262?s=12&t=AUhNsAKs8G7beopf-_iD3Q|Projected wayfinding in Newark Airport]]
newsletters/2025-02.1740777957.txt.gz · Last modified: 2025/02/28 21:25 by osnr

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki