Differences

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

--- newsletters:2024-11 [2024/12/01 03:50] – [Portable gadget] osnr
+++ newsletters:2024-11 [2024/12/01 04:09] (current) – osnr
@@ Line 1: / Line 1: @@
-====== November 2024 newsletter (WIP) ======
+====== November 2024 newsletter ======
 (Our next Folk open house is [[https://partiful.com/e/eZXJm5gn0rxglOGi5Jsa|at noon on Sunday, December 15]], at our studio in East Williamsburg, Brooklyn.)
@@ Line 22: / Line 22: @@
 There's still a lot of blinking under the new evaluator, but no ghosting, and I think the blinking all now emerges from genuine failures to meet timing (the label blinks out because the program region wasn't regenerated in time for the current frame).
+Notice how the camera hits 60fps but the full-frame detection is only 20-30fps (this is using a 1080p image):
+{{:newsletters:pasted:20241201-040919.png?550px}}
 === The bugfixes and improvements ===
@@ Line 43: / Line 47: @@
       * now runs on an independent clock from the frames! every 2ms
     * hack for 'descriptor indexing' on Pi GPU so images & text work
+    * incremental tag detection to be able to hit 60fps
@@ Line 73: / Line 78: @@
   * Sealed Tcl objects
     * I had been hoping to do this forever -- it seems elegant and cool and efficient -- but it turned out to be much harder than expected when I looked at it -- would need to change a lot of callsites in Jim Tcl (anywhere it shimmers an object) to make it work, or do horrible hacks with COW pages.
+    * {{:newsletters:pasted:20241201-040815.png?550px}}
   * CPU-oriented scheduling
   * Spinlocks
     * [[https://www.realworldtech.com/forum/?threadid=189711&curpostid=189723|Linus is probably right]]
     * I got too excited since we have fairly tight locking discipline in folk2
-    * Look at all this spinning:
+    * Look at all this spinning; it's not an improvement over mutexes:
       * {{:newsletters:pasted:20241201-034649.png?500px}}