3 ms·
Blazor is currenlty hobbled by having to haul its runtime across the wire and is thus not in a position to compete with React or Vue.
by cutler 6y ago
Blazor is currenlty hobbled by having to haul its runtime across the wire and is thus not in a position to compete with React or Vue.
- manigandham 6y agoThe server-side model doesn't have this issue and the client-side WASM model is brand new with the first production release a month ago so it will get better soon. The browser runtime is trimmed down to the APIs actually used, has dynamic async loading now, and it's around the 1.5MB mark which is competitive with the big SPA payloads.
- cutler 6y agoBut those "big SPA payloads" contain the whole app. With Blazor you incur a 1.5Mb overhead before you've written any app code. That's simply unacceptable on many devices so Blazor's current implementation is only relevant for internal apps.
- manigandham 6y agoSame with Blazor. The mon.wasm runtime is around 400kb compressed and the biggest DLL is mscorlib at 600kb. The actual DLLs for the app are just a few kb. Here's a very old build: https://blazor-demo.github.io/ https://blazor-demo.github.io/ And a recent build: https://stevesandersonms.github.io/BlazorOnGitHubPages/ https://stevesandersonms.github.io/BlazorOnGitHubPages/ Yes you can be smaller with JS but not by much these days, and given the amount of functionality you get with Blazor it's hard to compare on file size alone. Also if you're just making internal apps with controlled usage then server-side is better anyway.