"by the way, back on the topic of..." <- > <@jamesmunns:beeper.com> by the way, back on the topic of "maybe async": > > For people who WANT non-async drivers, how are you writing your code? I feel like doing anything non-trivial with blocking code requires SOME kind of concurrency, like RTIC, or an RTOS, or hand writing your own interrupts + state machines, etc. Are there really people who are writing things like that? And if so, how are you making that portable at all? Or am I underestimating how effective a single blocking "executive loop" is? Neotron OS and its various BIOSes do nothing off the sort. Nor do most Arduino programs. Nor do things running under MS-DOS. If you want a thing to happen, you do it, and wait until it is finished. You don't generally worry about other things happening whilst you are waiting - you will get around to them once you are done waiting. If you aren't chasing battery life, and the things you do don't usually take that long, this can be quite reasonable.