Adrian Cole

@gedw99 thanks when you have the doc together link it! For the conference, I'm not speaking, but there's a lot of wasm content there (also at rustlab). Mainly trying to...

fyi in a fairly upcoming release of zipkin, we will no longer advertise read endpoints for v1. You can follow issues on the main repo as I'm backporting conversion logic....

@mar1n3r0 I'll try to answer.. golang/go and tinygo-org/tinygo are alternative compilers of go source to WebAssembly. Both support `GOOS=js`, but at the moment only tinygo supports WASI for access to...

I think I need to defer to others, but last hint is that the people who maintain WASI are using interface types. [wit-bindgen](https://github.com/bytecodealliance/wit-bindgen) could have a plugin to generate tinygo...

Hi, I just tried to use the new wit format (WebAssembly Component Model). I think people will stick with witx for a while because it is quite opinionated. There are...

> Saw something about a new “unknown” triple target in tinygo which I think is trying to make the wasm have no std lib conceptually. > This seems to be...

@lthibault so there are a couple ways. * one way is to use a data binding approach such as https://github.com/knqyf263/go-plugin or https://karmem.org. * another is to define host functions that...

@lthibault PS the current best way to propagate extra stuff is via go context. we do it all the time now. I added an explainer here, but we probably need...

oh sorry my last reply was in general, not specific to GOOS=js. I'll update the PR description so I don't make that mistake again

@lthibault > Is it possible to rely on syscall/js functions to pass arguments to host functions? I'm trying to make a complex data type available to the guest, whose method...