2 ms·
What is the state of WASM support in Go though? :) I doubt the ability to cross-compile TSC would have been a major factor. These artifacts are always produced
by neonsunset 2y ago
What is the state of WASM support in Go though? :)
I doubt the ability to cross-compile TSC would have been a major factor. These artifacts are always produced on dedicated platforms via separate build stages before publishing and sign-off. Indeed, Go is better at native cross-compilation where-as .NET NativeAOT can do only do cross-arch and limited cross-OS by tapping into Zig toolchain.
- kokada 2y ago> What is the state of WASM support in Go though? :) I am sure it is good enough that the team decided to choose Go either way OR it is not important for this project. > I doubt the ability to cross-compile TSC would have been a major factor. I never said it was a major factor (I even said "I don't think it would be a deal breaker"), but it is a factor nonetheless. It definitely helps a lot during cross-platform debugging since you don't need to setup a whole toolchain just to test a bug in another platform, instead you can simple build a binary on your development machine and send it to the other machine. But the only reason I asked this is because I was curious really, no need to be so defensive.
- 9rx 2y ago> What is the state of WASM support in Go though? :) The gc compiler considers it a first-class build target. Like C#, the binary tends to be on the larger side[1], which makes it less than ideal for driving a marketing website, but that's not really a problem here. Installation of tools before use is already the norm. [1] The tinygo compiler can produce very small WASM binaries, comparable to C, albeit with some caveats (surprisingly, the extra data gc produces isn't just noise).