His talk was a major milestone in the arc of htmx, showing that a real world, commercial project could move from react to htmx and see significant benefits. I can't stress how important his talk was in the overall success of htmx, and I'm glad he followed up on it.
1. (Guile) Declare all the JS symbols you wish to use.
2. (JS) Write wrappers for the symbols from #1 above.
In short, you're still writing custom glue code for manipulating the DOM from the wasm language, and you'll need more custom glue code if you ever want to call your wasm functions from JS (for example, from the `onclick` attribute in an element tag, from `setInterval()`, from resolution of a promise, etc).
This is not what I meant by my response in the following exchange:
>>> It's true you have to use JavaScript glue code, but it's also true that won't be true forever.
>> I won't live forever and I'd like to deliver my product before I die.
Right now, it is true that wasm DOM access is non-existent, needs glue code to be existent, and the DOM <--> wasm interface, even with glue code, is limited as hell.
I don't know if there are plans to address this. It is irresponsible of me to use wasm for a client today under the assumption that, by the time I need a DOM <--> wasm interface, it will be there.
Before the limitations of the DOM <--> wasm interface is ever addressed, the product might even have reached end of life.
Re:Following up "Mother of all Htmx demos"
by itronitron on Saturday November 09, 2024 @01:36AM
(#42092886)
My only counter is that for a real-time collaborative app the server should be the single source of truth about application state, which would make htmx a good choice for that type of application.
https://htmx.org/essays/a-real-world-react-to-htmx-port/
His talk was a major milestone in the arc of htmx, showing that a real world, commercial project could move from react to htmx and see significant benefits. I can't stress how important his talk was in the overall success of htmx, and I'm glad he followed up on it.
Not any more. WebAssembly enables all languages on the client side.
Why am I using JavaScript when I can use anything else?
I won't live forever and I'd like to deliver my product before I die.
https://www.spritely.institute/news/building-interactive-web...
> https://www.spritely.institute/news/building-interactive-web...
That looks pretty damn onerous to me:
1. (Guile) Declare all the JS symbols you wish to use.
2. (JS) Write wrappers for the symbols from #1 above.
In short, you're still writing custom glue code for manipulating the DOM from the wasm language, and you'll need more custom glue code if you ever want to call your wasm functions from JS (for example, from the `onclick` attribute in an element tag, from `setInterval()`, from resolution of a promise, etc).
This is not what I meant by my response in the following exchange:
>>> It's true you have to use JavaScript glue code, but it's also true that won't be true forever.
>> I won't live forever and I'd like to deliver my product before I die.
Right now, it is true that wasm DOM access is non-existent, needs glue code to be existent, and the DOM <--> wasm interface, even with glue code, is limited as hell.
I don't know if there are plans to address this. It is irresponsible of me to use wasm for a client today under the assumption that, by the time I need a DOM <--> wasm interface, it will be there.
Before the limitations of the DOM <--> wasm interface is ever addressed, the product might even have reached end of life.
Making the next Figma? Hell no.
Adding some Ajax-y goodness to a legacy Django app? Sure.