In practice, if you’re going to make me have to use a promise to, say, decrypt 1kB of data using AES, I’m just going to use a wasm implementation of AES instead of turning my code into callback soup.
Well…I would assume this hypothetical coprocessor wouldn’t actually share the same memory as the host? That would be a bizarre implementation… Pretty sure you’d need to make the API not based on shared memory, anyway.
-
-
Yes, but just running async raises the possibility that the regexp itself could be mutated. This thought experiment may be fruitless (and regexps should not have been mutable! ;-). Better: if the API involves callbacks then it must be async. I still like your "blocks" definition.
-
This Tweet is unavailable.
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.