5 ms·

Congratulations! What are the next directions for the scripting language?

• recursivedoubts 6y ago
  I know htmx is a good idea, still waiting to see if hyperscript pans out. :) It still needs some pretty basic stuff like for loops and so forth. The goal is for it to be a embeddable, DOM-friendly & transparently asynchronous scripting language so you don't need to deal w/ callbacks: on click add .throb to me wait 3s remove .throb from me end I'd like to make ajax and web workers trivial to use from it. I hope to have a lot more time for it in the next year, now that htmx is stable. We'll see. Suggestions welcome! edit: one thing I'm pretty sure about is that I'm going to go back to an interpreted runtime over the transpilation I'm doing now
  • gmassman 6y ago
    What are the advantages of switching to an interpreted runtime? Btw I used htmx for a small project a few months ago and it was super easy to get working. Definitely recommend it, and looking forward to trying out 1.0 as soon as I have a chance!
    • recursivedoubts 6y ago
      more flexibility and easier to make it async-transparent since the interpreter runtime is basically a built in continuation system :)