3 ms·

I don't get it then; your fix to promises being complicated is to remove the ability to perform asynchronous actions. That's cool for a small scripting language

• recursivedoubts 4y ago
  hyperscript is designed for small, embedded front end scripting needs: toggling classes, listening for events from its sister project, https://htmx.org https://htmx.org, etc. It isn't a general purpose programming language for use, for example, on the server side in a node-like environment. you can still perform things asynchronously by wrapping any expression or command in an `async` prefix: https://hyperscript.org/commands/async/ https://hyperscript.org/commands/async/ but there isn't a mechanism for resolving all of them although, now, come to think of it, the following would work: set results to {result1: somethingThatReturnsAPromise(), result2: somethingElseThatReturnsAPromise()} That would work out because under the covers the hyperscript runtime calls a Promise.all() on those field values before it continues. Kind of a hack, but it would work. Anyway, again, hyperscript is a DSL targeted at small front end scripting needs rather than being a large scale concurrent systems programming language.