3 ms·

Because people don't want to load 300MB for a simple website (and this is blocking the first render, not just loading in the background). Not every language is

by gf000 10mo ago

Because people don't want to load 300MB for a simple website (and this is blocking the first render, not just loading in the background). Not every language is a good source for targeting WASM, in the sense that you don't want to bring a whole standard library, custom runtime etc with you. High-level languages may fare better if their GC is compatible with Wasm's GC model, though, as in that case the resulting binaries could be quite small. I believe Java-to-wasm binaries can be quite lean for that reason. In c#'s case, it's probably mostly blazor's implementation, but it's not a good fit in this form for every kind of website (but very nice for e.g. an internal admin site and the like)

sfn42 10mo ago
A modern blazor wasm app is nowhere near 300mb. There are techniques to reduce this size like tree shaking. There's no need to include lots of unused libraries. Modern Blazor can do server side rendering for SEO/crawlers and fast first load similar to next.js, and seamlessly transition to client side rendering or interactive server side rendering afterwards. Your info/opinion may be based on earlier iterations of Blazor.
michalsustr 10mo ago
300MB is nonsense, we are at 2MB compressed with https://minfx.ai https://minfx.ai
- doodlesdev 10mo ago
  > we are at 2MB compressed with https://minfx.ai That's still pretty bloated. That's enough size to fit an entire Android application a few years ago (before AndroidX) and simple Windows/Linux applications. I'll agree that it's justified if you're optimizing for runtime performance rather than first-load, which seems to be appropriate for your product, right?! What is this 2 MB for? It would be interesting to hear about your WebAssembly performance story! Regarding the website homepage itself: it weighs around 767.32 kB uncompressed in my testing, most of which is an unoptimized 200+kB JPEG file and some insanely large web fonts (which honestly are unnecessary, the website looks _pretty good_ and could load much faster without them).

by gf000 10mo ago

sfn42 10mo ago

A modern blazor wasm app is nowhere near 300mb. There are techniques to reduce this size like tree shaking. There's no need to include lots of unused libraries. Modern Blazor can do server side rendering for SEO/crawlers and fast first load similar to next.js, and seamlessly transition to client side rendering or interactive server side rendering afterwards. Your info/opinion may be based on earlier iterations of Blazor.

michalsustr 10mo ago

300MB is nonsense, we are at 2MB compressed with https://minfx.ai https://minfx.ai

doodlesdev 10mo ago
> we are at 2MB compressed with https://minfx.ai That's still pretty bloated. That's enough size to fit an entire Android application a few years ago (before AndroidX) and simple Windows/Linux applications. I'll agree that it's justified if you're optimizing for runtime performance rather than first-load, which seems to be appropriate for your product, right?! What is this 2 MB for? It would be interesting to hear about your WebAssembly performance story! Regarding the website homepage itself: it weighs around 767.32 kB uncompressed in my testing, most of which is an unoptimized 200+kB JPEG file and some insanely large web fonts (which honestly are unnecessary, the website looks _pretty good_ and could load much faster without them).