Viewing profile — adrianfcole
adrianfcole
HN member- Joined
- Fri, Aug 21, 2020, 12:26 PM UTC
- HN karma
- 24
- Public activity
- 16 items
- HN profile
- View on Hacker News ↗
About adrianfcole
No profile information was provided.
Recent public activity
-
comment
Comment #46242438
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 th…
-
comment
Comment #45863200
some of us still remember ;)
-
comment
Comment #35858668
(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 termin…
-
comment
Comment #35858646
(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. $ ec…
-
comment
Comment #35856631
(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 t…
-
comment
Comment #33718340
(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 rar…
-
comment
Comment #32573989
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 rel…
-
comment
Comment #31422428
thumbs up and subscribe to this :) https://github.com/tetratelabs/wazero/issues/577
-
comment
Comment #31416336
(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 you…
-
comment
Comment #31413777
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 incl…
-
comment
Comment #31413208
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 s…
-
comment
Comment #31412112
(wazero maintainer) The default implementation will compile WASM to assembly not at runtime, but AOT (during Runtime.CompileModule). This allows more consistent performance and als…
-
comment
Comment #31411828
(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 p…
-
comment
Comment #31411789
(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 …
-
comment
Comment #31411664
(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.co…
-
comment
Comment #31410310
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) […