Very timely, I've been working on Svelte integration for Phoenix Liveview, started working on it this week[1]. It's very cool to see LiveView expanding as a paradigm outside of Phoenix.<p>[1] <a href="https://github.com/woutdp/live_svelte">https://github.com/woutdp/live_svelte</a>
Great to see another language adopting LiveView! (Author of LiveViewJS[1] here).<p>Are you using Phoenix’s javascript client (and protocol) or rolling your own?<p>[1] - <a href="http://LiveViewJS.com" rel="nofollow">http://LiveViewJS.com</a>
> We’re actively working on adding accessibility support using the work done by EGUI as inspiration.<p>Glad to hear it. FWIW, I worked on the AccessKit integration in egui, as well as AccessKit itself, so let me know if you need help.
Dioxus liveview is so good.<p>I tried it with salvo and it just worked (tm).<p>The only downside which they're working on is some kind of socket reconnect if someone navigates away and the socket gets disconnected for some reason
On their github repo:<p>> Simple "hello world" at about 65kb, comparable to React<p>I assume that is minified and compressed. That's quite bloat. I wonder if they try <a href="https://github.com/johnthagen/min-sized-rust">https://github.com/johnthagen/min-sized-rust</a> ?<p>Also I feel like the BytecodeAlliance too much focus on their cloud runtime use case while seamless wasm + dom interop is where its adoption will skyrocking. I would rather write Rust/Go/Roc/any-sane-typing instead of TS.
I tried my best to browse all the docs and guides and sample code to know what does live view mean , but failed.<p>I guess this project's trying to make some buzzword ?<p>Because for documentation, assumption is bad.
Looks like a tyoo/error under lowercase components:<p>> Note that you still cannot define a one-word component without referencing it via path syntax.<p><pre><code> module::header {}
</code></pre>
Should be OK, not "x"?