4 ms·
> Well for Blazor Webassembly at least, you need to download the entire .NET runtime It's a one-time download that's smaller than the initial load of the Faceb
by brtkdotse 3y ago
> Well for Blazor Webassembly at least, you need to download the entire .NET runtime
It's a one-time download that's smaller than the initial load of the Facebook feed
- littlecranky67 3y agoplus in LOB apps very likely to be in the browsers cache already. And dont forget buisness workstations are usually connected via at least 1GBit Ethernet.
- guhidalg 3y agoI'm not who you're replying to but designing for excess resources is the kind of thinking that leads to slow software. > And dont forget business workstations are usually connected via at least 1GBit Ethernet. NOPE! More likely they are WiFi connected Dell shitboxes running Windows 11 with 8GB of memory, half of which is taken up by all the browser tabs, Teams, Office, and the 30 horrible little programs that IT deploys via group policy. Speed matters. The user is probably running your code + 30 other things. Don't assume your page is the only thing they care about.
- littlecranky67 3y agoAny data to back this up?
- LaGrange 3y agoAny data to back _your_ claims up? Because, y'know, sure, all _we_ have is years of lived experience.
- littlecranky67 3y agoIf your point is that companies run outdated, shitty computers connected over unreliable WiFi, _your_ corporate life experience has been vastly different than mine.
- Capricorn2481 3y agoWhat about the CPU usage? Facebook loads a lot of information. I don't think we should be comparing the download size of a hello world app with loading dozens of images on a facebook feed.
- deleted 3y ago[deleted]
- strich 3y agoHonestly I'm afraid you don't know what you're talking about. Blazor just isn't that experience and hasn't been for awhile.
- Capricorn2481 3y agoWell color me convinced!