3 ms·
The idea is that instead of shipping electron, you ship a native binary that use egui without using wasm or the canvas. Egui only use wasm in situations where
by jenadine 4y ago
The idea is that instead of shipping electron, you ship a native binary that use egui without using wasm or the canvas.
Egui only use wasm in situations where you must use the user browser because you have no choice. Eg: showing a demo of the app on the web without having to install anything.
> Its a 5mb wasm bundle. But on the plus side, 5mb is positively tiny compared to shipping electron
This comparison makes no sense. Situation where electron could be used are exactly the kind of situations where a wasm bundle would not be shipped (a native binary would be shipped instead)
- josephg 4y ago> This comparison makes no sense. Situation where electron could be used are exactly the kind of situations where a wasm bundle would not be shipped (a native binary would be shipped instead) Sure; but given the insane size of shipping chrome, it’s fun seeing a full app complete with widget library, layout engine and text input elements in 5mb. It’s terrible to make websites that big. But if chrome could do all that stuff in only a 5mb binary then I’d be much happier with electron. If you didn’t catch it, the wasm bundle is running in a 32mb memory slab. Positively slim by the standards of modern gui apps!