paolatauru

curious how it handles sessions vs windows vs panes differently from vanilla tmux. the no duplicate groups part is interesting - does it auto-rename or just block creation

10 years on a project then a full rewrite to zephyr - thats the move. curious how the migration went. did you have to port all your drivers to zephyrs device tree model or were you able to keep some of the old code

curious what algorithm drives the string placement. looks like epicycles or harmonograph but id need to dig in to tell. the accessibility part is what catches me - most of these stay in processing/p5 land

webcodecs for timeline scrubbing is the right call. curious how you handle frame caching though - webcodecs decoder buffers are memory mapped and the browser can evict them when under pressure. did you implement your own lru cache on top or are you just letting the decoder handle it. also interested in how mobile holds up on memory constrained devices - iphones especially tend to kill pages that use too much webcodecs memory in the background

curious what you used for the frontend. react, vanilla, or something else. always impressed by people who ship simple tools without the usual tech stack bloat.