sort of regretting having gotten a global-shutter webcam for Folk gadget (I think it makes it a lot harder to calibrate, because you can't capture the whole projector image without unwieldily huge exposure time)

ugh

currently resent this a little because the emitted error messages aren't greppable -- if you get the error "child killed by signal SIGUSR1", it's not obvious how to find its origin in this source code (the whole phrase won't work, "child killed by signal" won't work, and so on) without knowing exactly how it's chunked here

i forgot i wrote a paper about this for a class in college

the usual Arduino use of C++ is funny because the near-absence of heap allocation basically makes it look like Java -- no *s to be seen

realized i strongly associate rainbow palette with (non-CS) science and engineering visualizations and not with 'data visualization' culture https://mk.absturztau.be/notes/a6br8jrnzyhm00u1

i wonder if old pre-internet videophone systems actually felt different from modern video chat -- i could imagine them having way less latency because they could have a dedicated circuit connection and dedicated hardware on both sides, instead of webcam + OS + packet-switched internet that has tons of possible delays

Banana as free variable https://mastodon.online/@danielgibert/114275398786738404

was talking with people about structured concurrency a few weeks ago, and it does feel like an underrated part of making a responsive / concurrent 'OS' is the ability to *cancel* those concurrent tasks