https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • g
    (Yes, htmx is f'n rad)
  • m
    I can give much better runtime errors w/ an interpreted runtime
  • m
    i spent a lot of time transpiling it and now I think that, while I'll never forget those days, the good times and the bad, I'm going to now throw all that in the trash
  • g
    Yeah. Though, it's not throwing it away. It's learning and iterating on those lessons.
  • g
    Oh, another factor (still in favor of interpreting, I think)
  • g
    Which one will be easier for other developers to dig into, so that you're not the only one who has to do this.. all alone.. at 2AM.. crying into a bottle of tequilla?
  • m
    ☝️ 😑
  • f
    Yeah. I second what ben said.
  • m
    2021 is the year of hyperscript and I need to get serious about this thing. I think you are correct that we should focus on flexibility and maintainability
  • m
    One other nice thing about interpreted: each parse node effectively acts like a continuation, so my goal of transparent asynchronicity will be loads easier to implement
  • g
    Yes, and it potentially simplifies the goal of loading new fragments into the DOM, and only parsing them when they're needed.
  • m
    nobody ever got fired for creating an interpreted programming language
  • m
    they get fired for creating a programming langauge, period
  • m
    unless they are Rob Pike
  • g
    Plus, I'd really like to be able to send Hyperscript straight to the parser within my JS. Something like 
    <script>hyperscript.run('take green from #node then add #blue to #node')</script>
  • g
    Rob Pike is my spirit animal.
  • m
    bro
  • m
    plz
  • m
    Copy code
    html
<script type="hyperscript">take green from #node then add #blue to #node'</script>
  • g
    Yes. That's better.
  • m
    that will work one day, I promise
  • m
    OKOK
  • g
    But you'll still need a way to link into that from JS. I know I'm way outside of scope for right now, just planting seeds for 2021, the year of Hyperscript.
  • g
    But while I'm on the topic....
  • m
    yea
  • g
    How committed are you to making these two separate libraries? I think there's a lot of potential overlap (in the swapping logic alone) that might be useful to just combine them. They're each small enough that most people wouldn't mind a few extra K, but I think most use cases will need both tools anyway 🙂
  • m
    I'm going to add this:
    Copy code
    js
  on whatever log it then js {
    rawJavascriptShennanigans();
  }
  • m
    so you can inline JS in hyperscript
  • m
    it won't get the transparent asynchronousness, but thems the breaks
  • m
    hyperscript is already bigger than htmx
1...798081...1146Latest