3 ms·

I hope it's OK to add a shameless plug for my Rust WASM framework, Silkenweb [0]. It's similar to Leptos and Sycamore in that it's signals based, but I've put a

by ljsb 3y ago

I hope it's OK to add a shameless plug for my Rust WASM framework, Silkenweb [0]. It's similar to Leptos and Sycamore in that it's signals based, but I've put a lot of effort into making it ergonomic without resorting to a macro DSL. It supports all the usual things like SSR and hydration, along with a few nice extras like scoped CSS. [0] https://github.com/silkenweb/silkenweb https://github.com/silkenweb/silkenweb

7znwjshsus 3y ago
I love how simple your cargo toml is. A big turnoff of leptos for me was the incredibly messy cargo toml of the examples. I could barely touch it without bricking the project.
Firfi 3y ago
Author here! I've added it to my TODO list and will update the article at some point coming week or two. Love how the library looks like - thank you for the link!
davidatbu 3y ago
While I'm usually a no-macros kinda guy, but (I believe) leptos and dioxus provide tooling to hot-reload markup-only changes without (incremental) recompilation. Do you think that would be possible withour macros?
- ljsb 3y ago
  I can't think of any practical way to do that without macros, unfortunately. I've found incremental compilation to be pretty speedy for small markup changes so far though. I do tend to put the presentation code in it's own crate for larger projects, which might make a difference. Maybe as my projects get bigger I'll start to run into problems. Some other ideas: - Temporarily stopping the rust-analyser server to avoid lock contention on the build dir. - Using cranelift codegen backend (not sure of it's current status).
  - davidatbu 3y ago
    Thanks for the ideas! Separating out presentation crate into it's own crate sounds like a great idea. Re "temporarily stopping rust-analyzer", I came across this trick[0] to make RA use a different build path (trading off disk-space for speed, but I mean, disk space is cheap). Re: cranelift, I gotta check that out! Thanks for the reminder! [0] https://github.com/rust-lang/rust-analyzer/issues/6007#issuecomment-1379342831 https://github.com/rust-lang/rust-analyzer/issues/6007#issue...

by ljsb 3y ago

7znwjshsus 3y ago

I love how simple your cargo toml is. A big turnoff of leptos for me was the incredibly messy cargo toml of the examples. I could barely touch it without bricking the project.

Firfi 3y ago

Author here! I've added it to my TODO list and will update the article at some point coming week or two. Love how the library looks like - thank you for the link!

davidatbu 3y ago

While I'm usually a no-macros kinda guy, but (I believe) leptos and dioxus provide tooling to hot-reload markup-only changes without (incremental) recompilation. Do you think that would be possible withour macros?

ljsb 3y ago
I can't think of any practical way to do that without macros, unfortunately. I've found incremental compilation to be pretty speedy for small markup changes so far though. I do tend to put the presentation code in it's own crate for larger projects, which might make a difference. Maybe as my projects get bigger I'll start to run into problems. Some other ideas: - Temporarily stopping the rust-analyser server to avoid lock contention on the build dir. - Using cranelift codegen backend (not sure of it's current status).
- davidatbu 3y ago
  Thanks for the ideas! Separating out presentation crate into it's own crate sounds like a great idea. Re "temporarily stopping rust-analyzer", I came across this trick[0] to make RA use a different build path (trading off disk-space for speed, but I mean, disk space is cheap). Re: cranelift, I gotta check that out! Thanks for the reminder! [0] https://github.com/rust-lang/rust-analyzer/issues/6007#issuecomment-1379342831 https://github.com/rust-lang/rust-analyzer/issues/6007#issue...