Live data from Hacker News

Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

dioxuslabs.com

21–30 of 33 posts

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#21

On their github repo: > Simple "hello world" at about 65kb, comparable to React I assume that is minified and compressed. That's quite bloat. I wonder if they try https://github.com/johnthagen/min-sized-rust ? 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 ins…

How about assemblyscript?

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#22
post #7

Great to see another language adopting LiveView! (Author of LiveViewJS[1] here). Are you using Phoenix’s javascript client (and protocol) or rolling your own? [1] - http://LiveViewJS.com

We're using our own protocol right now - haven't really looked too deeply at the Phoenix protocol. We use templates (like Solid or Blockdom) to build and patch the page which is pretty specific to Dioxus.

Cool. We went with re-using/adopting Phoenix's because it is battle-tested and allowed us to not have to rebuild/find edge cases on browser event handling and DOM morphing and optimizing diffs. If you ever want a walk through lmk.

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#23
post #22

Earlier quoted context omitted.

We're using our own protocol right now - haven't really looked too deeply at the Phoenix protocol. We use templates (like Solid or Blockdom) to build and patch the page which is pretty specific to Dioxus.

Cool. We went with re-using/adopting Phoenix's because it is battle-tested and allowed us to not have to rebuild/find edge cases on browser event handling and DOM morphing and optimizing diffs. If you ever want a walk through lmk.

Is Phoenix's LiveView protocol documented anywhere? That would be pretty interesting reading.

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#25

On their github repo: > Simple "hello world" at about 65kb, comparable to React I assume that is minified and compressed. That's quite bloat. I wonder if they try https://github.com/johnthagen/min-sized-rust ? 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 ins…

How about assemblyscript?

AssemblyScript seems like a pointless also-ran. Why pick a language with very little support or community for your native code when you could pick Rust or C++? For any substantial app, I think an investment with Rust would be much better than an equal sized investment into AssemblyScript.

I think Rust will be around in 5 years. Will AssemblyScript?

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#26
post #25

Earlier quoted context omitted.

How about assemblyscript?

AssemblyScript seems like a pointless also-ran. Why pick a language with very little support or community for your native code when you could pick Rust or C++? For any substantial app, I think an investment with Rust would be much better than an equal sized investment into AssemblyScript. I think Rust will be around in 5 years. Will AssemblyScript?

It’s just a subset of TypeScript that compiles more directly to WASM and just as easily to JavaScript itself.

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#27
post #10

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. [1] https://github.com/woutdp/live_svelte

Cool. Can you use svelte stores across multiple liveview navigations?

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#28

On their github repo: > Simple "hello world" at about 65kb, comparable to React I assume that is minified and compressed. That's quite bloat. I wonder if they try https://github.com/johnthagen/min-sized-rust ? 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 ins…

How about assemblyscript?

It's okay. It actually produces the smallest wasm binary size AFAIK. I'm just tired of niche languages already. If I were to go niche why not https://grain-lang.org/ ? It's even a wasm-first lang. Zig is also good and produces small wasm binary. That said, I think Rust/Go is fine.

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#29
post #10

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. [1] https://github.com/woutdp/live_svelte

Cool. Can you use svelte stores across multiple liveview navigations?

That's something I need to look into. - Should be possible by saving the store in the localstorage and fetching it again on a different page. - Or saving the store to the window[1], as long as the page transitions happen through a live redirect[2] it should still be there.

I'm building a collection of examples[3] and if I can get it working I'll add it.

[1] https://wout.space/notes/how-to-share-store-between-multiple...

[2] https://hexdocs.pm/phoenix_live_view/live-navigation.html

[3] https://github.com/woutdp/live_svelte/tree/master/examples

Re: Dioxus 0.3 – Templates, Hot Reloading, LiveView, and More

#30
post #29

Earlier quoted context omitted.

Cool. Can you use svelte stores across multiple liveview navigations?

That's something I need to look into. - Should be possible by saving the store in the localstorage and fetching it again on a different page. - Or saving the store to the window[1], as long as the page transitions happen through a live redirect[2] it should still be there. I'm building a collection of examples[3] and if I can get it working I'll add it. [1] https://wout.space/notes/how-to-share-store-between-multiple…

Yea, for sure it should be possible to do it with local storage but the real cool thing would be to be able to keep state in js between live redirects. Like you said it should be possible if using live redirect. Would love that. Good luck! Hope to be able to use your library in the future.
Post reply on HN