Adding more failure points and complications may not increase the developer/business desirability to use Blazor for reaching the it possible that each component could get its own trimmed runtime, or otherwise somehow chunk and prioritize the payload so that, for example, users can start searching while the rest of the dashboard loads? And basically each component will get its own Blazor.start method for its packaged runtime, and only load the shared dependencies that component specifically needs to start. Blazor WASM and Server already have enough transient failure points that degrade the user experience. Is it possible that each component could get its own trimmed runtime, or otherwise somehow chunk and prioritize the payload so that, for example, users can start searching while the rest of the dashboard loads? And basically each component will get its own Blazor.start method for its packaged runtime, and only load the shared dependencies that component specifically needs to start.Īnd no offense but the hot switch between Blazor Server and WASM seems a bit shaky. Ok this may sound naive, but currently all the magic starts with Blazor.start at the bottom of the page. Prerendering with authentication is also something we're working on for. We are discussing how we might in the future enable a combined model where the app starts off with Blazor Server and then transitions to Blazor WebAssembly after the app has been downloaded. You're correct that prerendering only improves the perceived load time of the page.
0 kommentar(er)
