evacchi

9 ms·

61.
by evacchi 2y ago
@ncruces and I are also contributors to wazero, so ask away if you have questions :)
62.
by evacchi 2y ago
they are for Truffle-based language implementations https://chrisseaton.com/rubytruffle/pldi17-truffle/pldi17-tr...
63.
Yeti Programming Language(mth.github.io)
3 points by evacchi 2y ago|0 comments
64.
Apache Camel meets WASM – Part 1(lburgazzoli.github.io)
3 points by evacchi 3y ago|0 comments
65.
by evacchi 3y ago
There is also alf.io
66.
Wazero v1.6.0(github.com)
2 points by evacchi 3y ago|0 comments
67.
A Return to WebAssembly for the Java Geek(javaadvent.com)
2 points by evacchi 3y ago|0 comments
68.
Deep Dive into CheerpJ 3.0: A WebAssembly Java Virtual Machine for the Browser(labs.leaningtech.com)
6 points by evacchi 3y ago|0 comments
69.
by evacchi 3y ago
Maybe just the missing leading slash in the original reproducer? :)
70.
CobWeb: COBOL to WebAssembly Compiler(github.com)
14 points by evacchi 3y ago|0 comments
71.
by evacchi 3y ago
I don't know what kind of use case you have in mind specifically, but wherever you would use a scripting engine, you can embed a small Wasm runtime instead and let your end-users pick their favorite* language (*) as long as there is a
72.
by evacchi 3y ago
I am a fan of the Jacobin project! For your uses, you may also want to consider wazero [1], a pure-go WebAssembly runtime. Full disclosure: I am on the team :) [1]: https://wazero.io/
73.
by evacchi 3y ago
FYI: this builds cleanly with WASI SDK and runs with no changes in a Wasm runtime if you're into that kind of thing
74.
Asynchronous I/O in Windows for Unix Programmers(tinyclouds.org)
1 points by evacchi 3y ago|0 comments
75.
by evacchi 3y ago
worth mentioning: https://github.com/stealthrocket/timecraft full disclosure: I don't work on it, but the devs are committers/contributors to https://wazero.io (I am a wazero committer) :)
76.
by evacchi 3y ago
That is correct. It is a webassembly runtime that you can embed in your go project. There are also other wasm runtimes that run outside the browser, this is one written in Go
77.
by evacchi 3y ago
wazero is a wasm runtime , not a wasm compiler. For a compiler Go -> Wasm you should use tinygo or Go proper :)
78.
by evacchi 3y ago
so as for the first question, I'll refer to Adrian's reply on an older thread https://news.ycombinator.com/item?id=31415317 as for the second, that's an excellent question but I'll have to be honest and
79.
by evacchi 3y ago
We are tracking the evolution of most proposals but we are a tiny team so we try to concentrate our efforts on those that have a higher degree of maturity, but I am sure we will at some point :)
80.
by evacchi 3y ago
it's a bit more nuanced than that, we are also trying to actually limit third-party dependencies, you can read more about it here https://github.com/tetratelabs/wazero/blob/main/RATIONALE.md...
81.
by evacchi 3y ago
tinygo still wins for size, and the reflection story got better (json works!). The traditional Go compiler produces larger binary but OTOH it's super-fast, as fast as native builds!
82.
by evacchi 3y ago
The "zero-dependency" in this context really means zero dependencies from Cgo :) see https://news.ycombinator.com/item?id=36552401
83.
by evacchi 3y ago
wasmtime and wasmer are basically state-of-the-art. Our compilation backend is a fast, but straightforward translator from wasm to binary (think v8 liftoff vs turbofan), so it's faster than interpreting, but still slower than a well-cr
84.
by evacchi 3y ago
you mean like this? https://github.com/knqyf263/go-plugin ;) wazero under the hood, by one of our awesome community members
85.
by evacchi 3y ago
we have our own assembler for arm64 and asm64
86.
by evacchi 3y ago
as far as I know wazero is the only zero-dependency Wasm runtime written in Go. This is not just one of those "written in $LANG" kinda deal: most other runtimes require linking against a native library; this in turn plays against
87.
by evacchi 3y ago
It depends on what you mean for JIT. wazero is load-time AoT; i.e. we compile the module in-memory on load, for efficient execution later, when you instantiate, it is not AoT in the sense that we produce a stand-alone executable, the runt
88.
by evacchi 3y ago
Hey I am on the dev team if someone has questions :)
89.
Understanding WASM, Part 2: Whence WASM(neversaw.us)
4 points by evacchi 3y ago|1 comments
90.
by evacchi 3y ago
GOOS=wasip1 is pretty cool IMO (disclaimer: I work on wazero.io)

More ›