3 ms·
Dioxus 0.7 comes with a set of components that cover even most of interaction with the JS side. There are great times ahead. What seems to be missing is modular
by zoechi 1y ago
Dioxus 0.7 comes with a set of components that cover even most of interaction with the JS side. There are great times ahead. What seems to be missing is modularizing and lazy loading of the WASM moduls to reduce initial download size (I saw some experiments).
I immensely enjoy being able to use a sane language+tools for backend and frontend.
- weinzierl 1y agoDirect DOM access is missing. Until that WASM will always be only a second class citizen
- chamomeal 1y agoWill that ever be supported? I google it every six months or so and don’t see any promising news
- weinzierl 1y agoSame. It does not help that the whole thing also changes name all the time, so even finding out about the current state is a challenge.
- sjoedev 1y agoWASM does not need to access the DOM to be extremely useful. JS is already very effective and ridiculously fast for updating the DOM. WASM is to offload computationally expensive workloads that JS is not so good for (perhaps some sort of computer vision, for example). It passes the result back to JS to update the DOM.
- weinzierl 1y agoEveryone says that and it makes sense, so I don't criticize this opinion. And yet you have articles like OP, where someone finds WASM useful for form validation which is clearly not in the "offload computationally expensive workloads" category and would profit from a direct integration.
- tcfhgj 1y agoAccording to the developer of Leptos direct Dom access is barely relevant with respect to WASM webapps
- afiori 1y agoThe cost of not having direct dom access is that of a minimal js wrapper glue which is negligible,