there's a weird specific skill of looking at a bunch of papers and distilling them to 'this one proposes the actually useful technique in practice; all these others are later variations by other people that perform better on benchmarks but aren't really practical'

mulling whether to test Nvidia support by trying to set up Google Cloud Compute Engine workstation vs. trying to dig up my Jetson Nano and plug it into a spare display

they're both sort of weak, but the MS Bob approach actually seems slightly deeper than the Apple one / it takes the room/furniture/aesthetic at least a little bit seriously, instead of pasting a floating iOS on top https://olia.geocities.institute/@GIFmodel/111328018520066084

I was looking at "Pure" https://en.wikipedia.org/wiki/Pure_(programming_language) out of curiosity or maybe a desire for an alternative to Tcl (small language, simple syntax, term rewriting, barewords, JIT, ...), then realized it's not in Homebrew (https://github.com/agraef/pure-lang/issues/34), and _then_ realized that it's basically completely dead and nonviable because it depends on LLVM features that were removed after LLVM 3.5 https://groups.google.com/g/pure-lang/c/nd__RPNI36I

kind of surprises me that every scripting language doesn't have a sampling CPU profiler (that samples callstacks, lets you make a flamechart, etc) -- there are the built-in JS ones and py-spy and rbspy, but even those seem really recent to me

thinking of 'transmission over QR code on your phone screen' as an alternative to both wires and wireless. clearer mental model (of what's connected to what) than wireless + no need for physical wires or plugging into a port on your phone

I think making a live programming system that has to allow arbitrary systems programming sort of pushes you in this direction -- the most important thing is containing faults and not interrupting the entire system, instead of correctness, because you can fix correctness over time but if you hard crash then you're done https://social.omar.website/@omar/statuses/01HDE6DC7EJ7BG056PRV8V4PQK

I remember wanting to do a computer system along this line -- like Erlang to the max -- instead of guarding against errors, let things fail and contain the failure to a meaningful boundary (a specific process or module with limited state) and recover as fast as possible https://social.gfsc.studio/@nach/111283791813931656

I've been looking at this

http://www.ok.sc.e.titech.ac.jp/res/PCS/research/procamcalib/
https://github.com/bytedeco/procamcalib
http://www.ok.sc.e.titech.ac.jp/res/PCS/publications/procams2009.pdf

and am pretty excited/optimistic

but I feel like a decent number of people actually _do_ now learn/make music through DAWs or music programming languages which have that batch flavor https://social.tchncs.de/@daveliepmann/111274696437077402