4 ms·
Probably that Go has to ship heavier runtime (with its own GC etc)
by panstromek 2y ago
Probably that Go has to ship heavier runtime (with its own GC etc)
- jillesvangurp 2y agoProbably that. Kotlin waited until wasm GC was available and now has a compiler that relies on that. Kotlin wasm binaries can be pretty small depending on what libraries you use. Probably a bit of work but there should be no reason why Go would not be able to do the same at this point.
- pjmlp 2y ago.NET is still not using WASM GC for Blazor, because it doesn't support all the use cases in .NET runtime, that is the thing wiht having a single GC implementation for everyone. People tend to think all GC are the same, they are not.