Evan Almloff

Dioxus has runtime hooks that let you run code at specific points in the rendering lifecycle like `use_effect` which runs after the render. This issue sounds like it is mostly...

> Hm, I see. Dioxus hooks seems to follow roughly what solid does with it's reactive primitives, effects work the same way, memos work the same, and the basic reactive...

There are a few different ways to use `use_resource`: 1) The default `use_resource` without suspense will only run on the client in fullstack/ssg. This version will act like what you...

SolidJS does something interesting [here](https://docs.solidjs.com/reference/basic-reactivity/create-resource). They now expose a `ssrLoadFrom` option that sets the initial value for ssr and hydration and then reruns the future on the client. I agree,...

WASM also has limited support in dioxus fullstack. We cannot spawn threads or collect server functions automatically which makes starting dioxus fullstack more difficult. People have got it working with...

This is fixed in the 0.6.0-alpha. We no longer read the `Cargo.lock` file at all. Instead we look for assets in the link section of the binary cargo produces

This looks very similar to https://github.com/DioxusLabs/dioxus/issues/2732. See that issue for suggestions about what flags you can apply to strip that information from the binary. I don't think removing all tracing...

Hot reloading in 0.5 is limited to rsx that is not nested within other rust expressions like loops, if statements, components, and raw expressions. For example, this cannot be hot...

I think this is the same issue as https://github.com/tauri-apps/wry/issues/583 and this related windows behavior: https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/threading-model#reentrancy Our code lets you call new_window from the synchronous event handler which would be reentrant....

It looks like the apt cache action we are using is flakey. Last run failed to load the cache and silently continued to the next step, but it looks like...