Vibe-coded a YouTrack CLI tool in https://github.com/keithn/yt Also working on a language for embedded bare-metal devices with built-in cooperative multitasking. A lot of embedded projects introduce an RTOS and then end up inheriting the complexity that comes with it. The idea here is to keep the mental model simple: every `[]` block runs independently and automatically yields after each logical line of code. There i…
I've become more and more interested in code that yields (coroutines etc, read this fascinating article on HN just a couple of days ago: https://willhbr.net/2026/03/02/async-inject-and-effects/ )
Can you share more about this? How the async model works? Why it does -- is it a performance guarantee given the RTOS comment? Or is it more about the state machine idea, and how or why does yielding every line (not, say, every state transition, though I have no idea if or why that would be more useful) relate to that?
I mostly just have lots of questions because it sounds fascinating, so if you're looking for an excuse to talk about it, please count this as that excuse!