4 ms·
WASM is their weaker part. On the flip-side the WASM takeup is also rather modest so the net loss is not that big. Eventually they might come up with a solutio
by jhoechtl 6y ago
WASM is their weaker part. On the flip-side the WASM takeup is also rather modest so the net loss is not that big.
Eventually they might come up with a solution to get their huge WASM files down to bearable size. Sure its because they have to ship the bigger part of their VM with it.
- thefounder 6y agoI'm developing an entire desktop app in WASM(with electron). Once you build the right abstraction it's just Go...simple and fun! To me the main issue I have with Go is the incomplete reflect package(i.e StructOf )
- jhoechtl 6y agoSoemthing to show the world, github / -lab repo, the like?
- thegeekpirate 6y agoThere's no VM in Go—you're probably thinking of the runtime. A "Hello World!" using 1.15.4 on linux/amd64 takes up 1.2MiB of space (731KiB after UPX). Using https://github.com/tinygo-org/tinygo https://github.com/tinygo-org/tinygo, it drops to 21KiB (unable to be compressed further using UPX), making WASM size a non-issue.
- thegeekpirate 6y agoForgot to mention I was using TinyGo v0.15.0.