adrianfcole

8 ms·

1.
by adrianfcole 9mo ago
I feel you and I also think this is a tough time. I routinely use Claude even though he typically ignores me ;) I'm also a maintainer of Goose and have been engaged since before the rust rewrite. I'll admit I don't get exactl
2.
by adrianfcole 10mo ago
some of us still remember ;)
3.
by adrianfcole 3y ago
(wazero contributor) This is a fairly common problem in WebAssembly, jargon overload mixed with conflation. We're starting our own docs, and doing the rare thing of adding a terminology section to it ;) https://wazero.io&#x2
4.
by adrianfcole 3y ago
(wazero contributor) In case you are interested, you can use Ruby (or any other interpreter compiled to wasm) with wazero. Our CLI shows what most of the runtimes can do, too. $ echo salaboy | wazero run ruby-3.2.0.wasm -ne 'print &quo
5.
by adrianfcole 3y ago
(wazero maintainer) Right now, there's no auto-magic repackaging, but it is extremely common to do manually in our ecosystem. Most will use go:embed to embed the wasm binary into the compiled application so it still appears all static
6.
by adrianfcole 4y ago
(wazero contributor) thanks for the analysis. certainly dependency pain is something we hear about, as well as lack of maintenance on alternatives. Some don't release at all or rarely, and many break api constantly. We also break api,
7.
by adrianfcole 4y ago
As a relative newcomer to WebAssembly, the first thing I noticed was a disconnect between WebAssembly, which is loosely governed by W3C process, whereas WASI, a subgroup, never released a draft, closest thing being the module id people tend
8.
by adrianfcole 4y ago
thumbs up and subscribe to this :) https://github.com/tetratelabs/wazero/issues/577
9.
by adrianfcole 4y ago
(wazero maintainer) thanks for asking the questions! I'll answer them below. First as TL;DR; then more explained. TL;DR; > whats the compiled size? wazero adds less than 2MB to your binary with no strings attached. > Any performa
10.
by adrianfcole 4y ago
There's a proposals repo [1] that tracks the status of features like GC. According to that, GC is phase 2, which is prototyping [2]. To get to the finish line, implementations including at least 2 browsers need to happen (this is a Web
11.
by adrianfcole 4y ago
nope this is all under the scenes. We formerly called this JIT, which was inaccurate but removed this confusion. Calling it AOT is more precise, but people ask this question. win some you lose some I guess! Anyway, if you use `wazero.NewRun
12.
by adrianfcole 4y ago
(wazero maintainer) The default implementation will compile WASM to assembly not at runtime, but AOT (during Runtime.CompileModule). This allows more consistent performance and also more errors to materialize before a function call occurs.
13.
by adrianfcole 4y ago
(wazero maintainer) we have a popular allocation example, which shows how GC ends up embedded (really malloc/free) in wasm produced by Rust or TinyGo. You are right that whatever produces wasm, if needs to allocate memory, is doing tha
14.
by adrianfcole 4y ago
(wazero maintainer) no this doesn't really help with that. This runs wasm in Go, regardless of which language compiled to wasm. TinyGo [1] is the most popular option to compile Go into wasm, and they have some instructions for web brow
15.
by adrianfcole 4y ago
(from wazero maintainer) we run benchmarks [1] on every commit! Depending on host and CI weather, we sometimes don't win [2] (click the Run make.check thingy) [1] https://github.com/tetratelabs/wazero/tree&#x2
16.
by adrianfcole 4y ago
I'm a maintainer on wazero. We have two things in progress on debugability, though both are stalled as we complete the recently announced WebAssembly 2.0 draft spec (nearly done) [1]. 1. DWARF support - this requires those compiling to