4 ms·

Oops, those docs need updating. The GC now works on all platforms (including RISC-V and WebAssembly!) except for AVR because the AVR backend is just too unrelia

by aykevl 7y ago

Oops, those docs need updating. The GC now works on all platforms (including RISC-V and WebAssembly!) except for AVR because the AVR backend is just too unreliable at the moment and you wouldn't want a GC in 2kB of memory anyway.

owaislone 7y ago
GC works even in WASM? That's great! What size wasm targets does TinyGo generate compared to the regular Go compiler?
- sendilkumarn 7y ago
  It produces much smaller binaries My blog post on it -> https://dev.to/sendilkumarn/tiny-go-to-webassembly-5168 https://dev.to/sendilkumarn/tiny-go-to-webassembly-5168
- justinclift 7y ago
  In the (reasonably simple) stuff we've been doing so far, TinyGo produced wasm files are 2-3% the size of mainline Go produced wasm files. eg: https://justinclift.github.io/tinygo_canvas2/ https://justinclift.github.io/tinygo_canvas2/ (~19.5kB) https://justinclift.github.io/tinygo-wasm-rotating-cube/ https://justinclift.github.io/tinygo-wasm-rotating-cube/ (WebGL, ~12kB)
mntmoss 7y ago
That's wonderful to hear, I just wish I had learned about it sooner. I kept looking back at TinyGo for WASM tasks, because it looked like the right combo of size footprint and runtime capabilities, then ultimately thinking "hmm but the GC issue." I'll probably take a look later today!