3 ms·

The async transparency aspect is very interesting from a design POV! What were your inspirations for that?

recursivedoubts 6y ago
I just hated the way that callbacks look or that you had to color your functions: https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/ https://journal.stuffwithstuff.com/2015/02/01/what-color-is-... For light weight scripting I didn't want to have to think about that. I had implement a "wait" command in the old ic-action attribute from intercooler: https://intercoolerjs.org/attributes/ic-action.html https://intercoolerjs.org/attributes/ic-action.html And I wanted to generalize that. (A motivation for creating _hyperscript was because I removed ic-action as well as a bunch of other event-based attributes when rewrote intercooler.js as htmx: https://hyperscript.org/docs/#history https://hyperscript.org/docs/#history)
- mstade 6y ago
  The async transparency stuff is really interesting, and reminds me of a comment[1] I made a couple of years ago here on HN about async/await and how I think it's backwards from what it ought to be. Really glad to see you exploring this further, I think you're on to something. That post from Bob Nystrom's blog makes the point I was trying to make much more eloquently than I could, thanks for sharing! [1]: https://news.ycombinator.com/item?id=21065806 https://news.ycombinator.com/item?id=21065806
  - recursivedoubts 6y ago
    Yeah, it's really annoying that if you want to introduce some async behaviour in a function, you end up having to deal with it at all the call sites In the intro section I walk through adding a fetch to some code that jams text into a button and you can see how you don't end up having to change your code to do it: you just write the normal linear code with a fetch command in it: https://hyperscript.org/docs/#introduction https://hyperscript.org/docs/#introduction <button class='btn primary' _="on click fetch /clickedMessage then transition opacity to 0 put the result into me then transition opacity to 1 wait 2s then transition opacity to 0 put 'Click Me!' into me then transition opacity to 1"> Click Me! </button> The fetch, wait and transition commands are asynchronous (in javascript terms) but to hyperscript it's all just linear code.

I just hated the way that callbacks look or that you had to color your functions: https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/ https://journal.stuffwithstuff.com/2015/02/01/what-color-is-... For light weight scripting I didn't want to have to think about that. I had implement a "wait" command in the old ic-action attribute from intercooler: https://intercoolerjs.org/attributes/ic-action.html https://intercoolerjs.org/attributes/ic-action.html And I wanted to generalize that. (A motivation for creating _hyperscript was because I removed ic-action as well as a bunch of other event-based attributes when rewrote intercooler.js as htmx: https://hyperscript.org/docs/#history https://hyperscript.org/docs/#history)

mstade 6y ago
The async transparency stuff is really interesting, and reminds me of a comment[1] I made a couple of years ago here on HN about async/await and how I think it's backwards from what it ought to be. Really glad to see you exploring this further, I think you're on to something. That post from Bob Nystrom's blog makes the point I was trying to make much more eloquently than I could, thanks for sharing! [1]: https://news.ycombinator.com/item?id=21065806 https://news.ycombinator.com/item?id=21065806
- recursivedoubts 6y ago
  Yeah, it's really annoying that if you want to introduce some async behaviour in a function, you end up having to deal with it at all the call sites In the intro section I walk through adding a fetch to some code that jams text into a button and you can see how you don't end up having to change your code to do it: you just write the normal linear code with a fetch command in it: https://hyperscript.org/docs/#introduction https://hyperscript.org/docs/#introduction <button class='btn primary' _="on click fetch /clickedMessage then transition opacity to 0 put the result into me then transition opacity to 1 wait 2s then transition opacity to 0 put 'Click Me!' into me then transition opacity to 1"> Click Me! </button> The fetch, wait and transition commands are asynchronous (in javascript terms) but to hyperscript it's all just linear code.