10 ms·
Is it, actually? I mean, yes of course its 45MB difference, but does this matter? We are not talking about applications downloaded to a browser (webapp) or to a
by littlecranky67 6y ago
Is it, actually? I mean, yes of course its 45MB difference, but does this matter? We are not talking about applications downloaded to a browser (webapp) or to a mobile phone. In a time where I download >50GB+ games on Steam and deploy from CI/CD server or docker registries to my servers, is a size of 50MB or 100MB really a showstopper?
Don't get me wrong, I totally love 4k and 64k demos and am always fascinated what could be packed into such small binaries, but in my professional life I think developer productivity, code quality and tooling is way more important than filesize. This is of course different if you are a webdev that ships .js, or an App developer publishing to Appstores.
- tyrrrz 6y agoThe only environments where self-contained deployment matters are the ones you mentioned: browser, mobile phone, and also desktop. So yes, 45mb is a big difference (actually my app is 250mb).
- ablekh 6y agoIn the .NET context, browser-targeted deployments can have a minimal download overhead of around 2 MB, which is a far cry from 50 MB. How? Blazor. For details, see https://blog.ndepend.com/blazor-internals-you-need-to-know https://blog.ndepend.com/blazor-internals-you-need-to-know.
- cutler 6y agoThat's 2Mb front-end which is quite heavy.
- ablekh 6y agoHow 2 MB could be considered heavy, when visiting most websites results in much larger sizes of downloaded resources?
- littlecranky67 6y agotell that to websites auto-playing videos (in muted state) or even better, using videos as page background that play without interop.