If I get this correctly, both this and Blazor are handling most of the UI logic in front-end, despite they are WASM.
So WASM is just another bytecode encoding that relatively smaller than JavaScript, without solving the problem from the root.
In contrast, a server-side heavy solution like Phoenix LiveView that has been heavily mentioned in this thread would do hold the logic on the server side, so in the client, there's only very few generic logic handling the DOM patching.
Comments
If I get this correctly, both this and Blazor are handling most of the UI logic in front-end, despite they are WASM.
So WASM is just another bytecode encoding that relatively smaller than JavaScript, without solving the problem from the root.
In contrast, a server-side heavy solution like Phoenix LiveView that has been heavily mentioned in this thread would do hold the logic on the server side, so in the client, there's only very few generic logic handling the DOM patching.