Memory usage difference should be something like an order of magnitude better with .NET.
It's not a direct comparison, because the features aren't quite the same, but the Electron Teams app uses about 10x more memory than the relatively heavy WPF Skype for Business client that it's supposed to replace.
Would be nice to get a source for this interesting claim.
But I'm far more interested by real world user facing performance metrics such as:
FPS, vsync consistency, input latency and comparing cpu and gpu usage (thus allowing to infer battery usage).
If you were knowledgeable, you would know for example that chromium 2D rendering engine (skia) is the current state of the art.
Benchmarking fps, vsync stability, input latency, etc would be enlightening.
There are order of magnitude more engineers working at optimizing chromium than WPF.
I think the OP meant "bloated and heavy" in terms of the sheer size of the thing, not the performance of it. And it is. It's very difficult to use _just_ the 2D rendering part of Chromium, you bundle the whole thing, warts and all.
Binary size is only one "performance metric" and arguably the less important one.
Anyway, did you know that chromium is the GUI framework that allow you to have the smallest Binary size?
Instead of bundling it like you would with most GUI frameworks (GTK, QT) you can just use the locally installed chrome instance through Carlo.
It's not a direct comparison, because the features aren't quite the same, but the Electron Teams app uses about 10x more memory than the relatively heavy WPF Skype for Business client that it's supposed to replace.