**Kit Redgrave 🕯** @KitRedgrave@glitch.social · Jun 20, 2018, 19:06

**Kit Redgrave 🕯** @KitRedgrave@glitch.social · Jun 20, 2018, 19:06

Kit Redgrave 🕯 @KitRedgrave@glitch.social

Jun 20, 2018, 19:06

Kit Redgrave 🕯 @KitRedgrave@glitch.social

async stuff, js musing Show more

i keep thinking that all of these callbacks might be better organized in, like, a state machine or something instead of just pyramiding out to the right

**Kit Redgrave 🕯** @KitRedgrave@glitch.social · Jun 20, 2018, 19:08

**Kit Redgrave 🕯** @KitRedgrave@glitch.social · Jun 20, 2018, 19:08

Jun 20, 2018, 19:08

Kit Redgrave 🕯 @KitRedgrave@glitch.social

async stuff, js musing Show more

all of your event callbacks could then just look up what the current state is, and invoke the corresponding state transition function attached to it

**Christopher Lemmer Webber** @cwebber@octodon.social · Jun 20, 2018, 19:10

**Christopher Lemmer Webber** @cwebber@octodon.social · Jun 20, 2018, 19:10

Jun 20, 2018, 19:10

Christopher Lemmer Webber @cwebber@octodon.social

async stuff, js musing Show more

@KitRedgrave async / await makes this a bit better in javascript

BUT STILL

the right answer is to have coroutines (ideally by delimited continuations) in a way that's much more cleanly baked into the language

Racket / Guile do this in a sane way. async stuff can be made completely clean and look like everyday straightahead coding.

Every time I program in javascript I get so angry because of this.

**Jamey Sharp** @jamey · 2018-06-20T19:21:05Z

Jamey Sharp @jamey

async stuff, js musing Show more

@cwebber @KitRedgrave I love Simon Tatham's "Coroutines in C", have you seen that?

https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html

It's so delightfully horrifying, and made even better/worse by the follow-up:

https://www.chiark.greenend.org.uk/~sgtatham/mp/

Anyway there are an amazing variety of ways to do this kind of thing in many languages and I love them all and want everybody to see them 😅

Jun 20, 2018, 19:21 · Web · 1 · 5