long essay about coroutine philosophy(!) that I just saw https://www.chiark.greenend.org.uk/~sgtatham/quasiblog/coroutines-philosophy/

social media https://searchhistory.site

"heating is really easy, and cooling is really hard, which is a general unfortunate engineering reality of all systems"

sort of a C++ energy here https://front-end.social/@matuzo/114075968615875947 -- where for historical reasons you end up with 200 ways to do anything that are all slightly different from each other

https://www.are.na/omar-rizwan/when-we-understand-that-slide-we-ll-have-won-the-war

(this feels like sort of a cheap shot, though, like when people complain that it's hard to make a formal grammar for Markdown or a formal semantics for C)

i was talking to maxbittker about this https://gwern.net/doc/technology/2004-03-30-shirky-situatedsoftware.html reading it now it feels like the predictions are totally wrong even though the observations are correct -- if anything the opposite of what it predicted has happened

remembering when my code worked on Linux (radio) but not on macOS (my laptop) because I forgot to initialize a pthread_mutex_t, which apparently means the mutex still blocks properly on Linux but it doesn't do anything on macOS

sort of annoying realization that the Tcl notion of immutability is not really the same as the thread-safe notion of immutability -- Tcl immutability still lets you arbitrarily shimmer the internal representation of a value so you can efficiently operate on it (as long as the value would still serialize to the same string), which is obviously not thread-safe

making fun of code formatter people by creating a word processor where you just type in words and the software (using AI or whatever) automatically adds all the punctuation and paragraph breaks where *it* thinks is appropriate

Logo as a product of its time