writing about some of the architectural challenges of making deeply flexible and extensible experimental frameworks I'm gonna be working on over here
after a number of rebuilds reflective of the challenge of hardware control on the raspi, we'll be clarifying the inheritance system to use backends as parallel mix-ins. rather than optimizing one system we'll work on making a clear path to define them
semantic wikis are powerful for communal development- creating multiple, mutually reinforcing means of interacting with a tool. combined with a plugin system (itself using the wiki), thinkin bout a different way of combining technical knowledge with code https://twitter.com/auto_pi_lot/status/1478987157058453505?t=ZTzF-7XnYPgSCwI-ThBakw&s=19
this thread a tiny tiny example of why this is hard to do and how architecture of a tool is not neutral to the kind of use patterns it supports. (the STS ppl will roast me for saying the obvious) https://twitter.com/auto_pi_lot/status/1478986353408811008?t=ZTzF-7XnYPgSCwI-ThBakw&s=19
if we want to break down papers as the fundamental unit of scientific knowledge, uniquely unfit for local technical knowledge like this, I think investing in alternative communicative systems is necessary, and by linking them with practical tools we might even make it useful.
A Fediverse instance for people interested in cooperative and collective projects.