4 ms·
Did you miss this part: >1) a websocket-based HTML sync layer, basically shipping over the smallest amounts of render state from the back-end. This is as close
by learc83 6y ago
Did you miss this part:
>1) a websocket-based HTML sync layer, basically shipping over the smallest amounts of render state from the back-end. This is as close as you get to having, essentially, a server-side rendered page that is then updated in real time.
Also it's not like you have to load the runtime more than once. So it's not that it's a non-starter for anything performance sensitive--it's a non-starter for anything that can't download a 2MB file up front (I believe their goal is to get it down to half that size) if you want to use the WASM version of Blazor instead of the websocket-based HTML sync layer version.
- cutler 6y agoCompared to React + React DOM at 109k unzipped Blazor's runtime at 2MB is a significant hike in download size so unsuitable for older devices and constrained bandwidth networks.
- learc83 6y ago1. Being too large for constrained bandwidth networks hardly makes it a non starter for anything performance sensitive unless you have a very narrow definition of performance. 2. 2MB includes bootstrap CSS and they are working on getting that number down. 3. 2MB is only the Wasm version of Blazor. You don’t have to use that version if it doesn’t fit your use case.
- cutler 6y agoI don't have to use it but Wasm Blazor is the version everyone is shouting about. Well, everybody at the Microsoft hype machine that is.
- learc83 6y agoGo to the Blazor homepage. Right there on the front page--the 2nd bullet point is "Run on WebAssembly or the server". Most people I've talked to using Blazor are in fact using Blazor server not Blazor WASM.