@Orion Reed and I submitted a positional paper for LIVE 2025 called "Live Programming in Hostile Territory". Now that it's been accepted, I'm excited to hear peoples thoughts and feedback! It touches on a topic wider than just live programming and, at least to me, is very relevant to the FOC community. Here is the abstract: > Live programming research gravitates towards the creation of isolated environments whose success is measured by domination: achieving adoption by displacing rather than integrating with existing tools and practices. To counter this tendency, we advocate that live programming research broaden its purview from the creation of new environments to the augmenting of existing ones and, through a selection of prototypes, explore three adversarial strategies for introducing programmatic capabilities into existing environments which are unfriendly or antagonistic to modification. We discuss how these strategies might promote more pluralistic futures and avoid aggregation into siloed platforms. https://folkjs.org/live-2025/

All I can say is I'm in favor of adversarial interop! :D

awesome piece, it made me think that targeting a static HTML file as a programming environment is not far enough, I should be aiming to target a div, wherever it may be (e.g. on someone else's website).

I'm partial to the "competitive compatibility" phrasing, and AIs are proving especially good with the gross glue and shady shims that help get systems to talk to each other.

@Tom Larkworthy ha love it! I think you'd like this POC we have of HTML pipes to author computational notebooks with one new custom HTML element https://folkjs.org/demos/pipes.html

Yes, for your instance, the choice of terminology is good.

Oh

folk-pipe

is great! https://github.com/folk-js/folkjs/blob/main/packages/labs/src/folk-pipe.ts Observable has Generator.input which listens to events and streams the values too (here). Thats the HTML -> reactive value direction. It does not have the other direction AFAIK, been looking for something! I only recently realized JS Generators have the resource tidy up built in

Generator.prototype.return

. Worth knowing about if you not noticed, as they compose with js language features like yield * and for .. of.