Philipp Tessenow

I _think_ i can report progress. I just pushed another (still very broken) version of wasmex-wasmtime which introduces a new concept * during function execution we get the `caller` struct...

Good news! together with @hamptokr we could fix the memory problem and reading/writing memory from within function calls now fully works. In fact, all tests - with the exception of...

Keeping you updated here: WASI seems to work roughly - I still have to fix file access permissions, but 5/10 wasi tests work. This is getting closer :)

super exciting indeed! :) I worked some more on the wasmtime fork and all test are green now 🎉 However, it works only on [my wasmtime fork](https://github.com/tessi/wasmtime). Next task is...

However, @brooksmtownsend it would be great if you could give that fork a try and see if it works for you. Some things (especially the WASI API) changed, but I...

😊 thanks everyone! didn't mean this to be hunting for compliments 🙈 > we are actually thinking about creating an abstract API on top of those SDKs to support easy...

I'm not an artist of any kind, so bear with me. But what about using a pipette as the logo? Pipettes are a tool to work with drops of elixir,...

> Next task is to contribute my wasmtime changes back so we can have proper access permissions for preopened directories. Turns out that [the wasmtime folks recommended to not have...

@brooksmtownsend did you have the time to try things out yet? No worries if not :) I'll soon merge my work back into this repo (in some dev-branch, I guess)...

The [MR that brings the changes back](https://github.com/tessi/wasmex/pull/385) is here and looks good. Docs are updated, changelog is written.