35.8 mb of ressources
for a calculator...
how can people be fine with that and press the publish button?
35.8 mb of ressources
for a calculator...
how can people be fine with that and press the publish button?
It's definitely too large, and that is the current state of .NET running on WebAssembly, where missing WebAssembly features (like exception handling) are forcing the compiler to generate a lot of code to compensate.
Still, we have one issue in this build where the PWA webworker doubles parts the payload, but even at ~25MB, it is still too big even if it is downloaded once and cached. For reference, the original windows version is around 13MB on disk for x86.
The point of the Calculator exercise is to show the ability to port the Windows calculator as-is (though translated from C++ to C#) to multiple non-Windows platforms. We continue working on that to improve the payload size and performance further, following WebAssembly, browsers and the .NET runtime advances.
kaz 22301 0.0 0.0 25188 7264 pts/2 Ss+ Nov03 0:02 bash
kaz 25976 0.0 0.1 27268 9632 pts/1 Ss Nov16 0:08 bash
kaz 27179 0.0 0.0 24368 6704 pts/0 Ss Nov16 0:01 bash
^^^^^ ??
EMACS = Eight Megabytes and Constantly Swapping used to be a ha-ha only not funny joke. PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
2048 REDACTED 20 0 12852 1844 1816 S 0.0 0.0 0:00.01 │ bash
Ubuntu 20.04 with latest patchesI was thinking, "man, this is nicely responsive and usable; how much RAM is in this thing?"
I drop to the shell to run "free" ... 6 megs!
Remembering these things is important, kind of like remembering rivers full of fish, frozen polar ice caps, or the song of an extinct bird.