Hi, Uno Platform dev here. We're not fine with the current payload size of the application, really.

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.

Then maybe don't showcase it so prominently. I bet this demo is what about 90% of people interested in Uno check out and my perception was certainly "wow, this performs badly", tainting my perception of the whole thing.

The same way they can be fine with a bash processes having 24 megabyte VM footprints.

  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.

That does seem weird. Just checked my bash processes and none exceed 13 megabytes of virtual memory

  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 patches

I remember a moment from 1994 or so. I was using a friend's machine, which was running X on top of Linux. It was some model of 486. I had some image viewing windows open (xv program), and was editing a complex figure in XFig, and had some audio playing.

I 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.

The same that would otherwise create a react app to display static text or an image gallery.