5 ms·

You might want to read the TFA, it's describing a "whole other language" they call Hyperscript on click send htmx:abort to #contacts-btn on htmx:before

You might want to read the TFA, it's describing a "whole other language" they call Hyperscript on click send htmx:abort to #contacts-btn on htmx:beforeRequest from #contacts-btn remove @disabled from me on htmx:afterRequest from #contacts-btn add @disabled to me

mega_tux 2y ago
Hyperscript is totally optional, you can use vanilla js or something like alpinejs for extra stuff
recursivedoubts 2y ago
hyperscript is a completely separate technology from htmx, it is designed to be an alternative to javascript and is very speculative htmx generalizes hypermedia controls, that's pretty much it, and it can be used with any scripting tool you'd like: AlpineJS, hyperscript (if you are brave), vanilla js, etc.
- troupo 2y ago
  All the hx-* attributes constitute a separate DSL with its own semantics and it requires the server to conform to this DSL that also subsumes a bunch of existing HTTP semantics like redirects.  <div hx-get="/example" hx-swap="innerHTML show:#another-div:top"> Get Some Content </div>  <div hx-get="/clicked" hx-trigger="click[checkGlobalState()]">Control Click Me</div>  <div hx-get="/example" hx-trigger="keyup" hx-vals='js:{lastKey: event.key}'> <input type="text" /> </div>  <button hx-get="/info" hx-on::before-request="alert('Making a request!')"> Get Info! </button> <button hx-get="/info" hx-on="htmx:beforeRequest: alert('Making a request!') htmx:afterRequest: alert('Done making a request!')"> Get Info! </button> And so on.
  - dartos 2y ago
    The point isn’t to erase the need for JavaScript entirely, but to make it possible to integrate and interact with a backend in a meaningful way using just mainly html.
    - troupo 2y ago
      That literally isn't what I talked about.
      - dartos 2y ago
        3 out of 4 of your examples mentioned using js or a js-like DSL. Explain your point better
        troupo 2y ago
        It's enough to read the context of the discussion, don't you think? Original complaint: "it's describing a "whole other language" they call Hyperscript" Response: hyperscript is a completely separate technology. htmx generalizes hypermedia controls, that's pretty much it, and it can be used with any scripting tool you'd like My response: In reality [1] htmx defines its own non-optional DSL that you have to use. --- I will add that as with any organically grown nice-to-have utility DSLs it's quite haphazard (it's hyperscript-like in one place, js-like in another place, both in some other places etc.). But that's the nature of such ad-hoc informally specified DSLs [1] which can be easily verified by just visiting https://htmx.org https://htmx.org
        deleted 2y ago
        [deleted]
        ungamedplayer 2y ago
        > In reality [1] htmx defines its own non-optional DSL that you have to use. --- I don't use hyperscript with my htmx, ergo it IS optional in objective reality. Citing a use with it does not prove it can't be used without it.

mega_tux 2y ago

Hyperscript is totally optional, you can use vanilla js or something like alpinejs for extra stuff

recursivedoubts 2y ago

hyperscript is a completely separate technology from htmx, it is designed to be an alternative to javascript and is very speculative htmx generalizes hypermedia controls, that's pretty much it, and it can be used with any scripting tool you'd like: AlpineJS, hyperscript (if you are brave), vanilla js, etc.

troupo 2y ago
All the hx-* attributes constitute a separate DSL with its own semantics and it requires the server to conform to this DSL that also subsumes a bunch of existing HTTP semantics like redirects.  <div hx-get="/example" hx-swap="innerHTML show:#another-div:top"> Get Some Content </div>  <div hx-get="/clicked" hx-trigger="click[checkGlobalState()]">Control Click Me</div>  <div hx-get="/example" hx-trigger="keyup" hx-vals='js:{lastKey: event.key}'> <input type="text" /> </div>  <button hx-get="/info" hx-on::before-request="alert('Making a request!')"> Get Info! </button> <button hx-get="/info" hx-on="htmx:beforeRequest: alert('Making a request!') htmx:afterRequest: alert('Done making a request!')"> Get Info! </button> And so on.
- dartos 2y ago
  The point isn’t to erase the need for JavaScript entirely, but to make it possible to integrate and interact with a backend in a meaningful way using just mainly html.
  - troupo 2y ago
    That literally isn't what I talked about.
    - dartos 2y ago
      3 out of 4 of your examples mentioned using js or a js-like DSL. Explain your point better
      - troupo 2y ago
        It's enough to read the context of the discussion, don't you think? Original complaint: "it's describing a "whole other language" they call Hyperscript" Response: hyperscript is a completely separate technology. htmx generalizes hypermedia controls, that's pretty much it, and it can be used with any scripting tool you'd like My response: In reality [1] htmx defines its own non-optional DSL that you have to use. --- I will add that as with any organically grown nice-to-have utility DSLs it's quite haphazard (it's hyperscript-like in one place, js-like in another place, both in some other places etc.). But that's the nature of such ad-hoc informally specified DSLs [1] which can be easily verified by just visiting https://htmx.org https://htmx.org
        deleted 2y ago
        [deleted]
        ungamedplayer 2y ago
        > In reality [1] htmx defines its own non-optional DSL that you have to use. --- I don't use hyperscript with my htmx, ergo it IS optional in objective reality. Citing a use with it does not prove it can't be used without it.