4 ms·

I think the wasm C API is not going to live up to the promise. To actually use high performance features you need many additions to that API that most implement

I think the wasm C API is not going to live up to the promise. To actually use high performance features you need many additions to that API that most implementations provide, thus making it less portable. Source: I contribute a lot to wasmtime’s C API and build Redpanda’s Wasm Data Transforms using it

cornstalks 3y ago
Yeah and wasm-c-api has stalled (they still don’t support v128, for example). I’m currently exploring starting an unsanctioned v2 wasm-c-api that aims to be feature complete and hopefully more performance focused.
- rockwotj 3y ago
  Would be super interested in this if you explore this more! Feel free to reach out (contact info linked from my bio) if you’re interested in collaborating.
kelp 3y ago
I'd been hoping projects like wasmtime could end up looking like a Docker alternative for server side things. Do you think that's unlikely to pan out without a lot more work that doesn't seem to be happening?
- rockwotj 3y ago
  Oh it’s certainly looking like that IMO depending on your use case for docker You can run wasm in k8s: https://krustlet.dev/ https://krustlet.dev/ Docker itself can run wasm: https://wasmlabs.dev/articles/docker-without-containers/ https://wasmlabs.dev/articles/docker-without-containers/ There are a few serverless runtimes based on wasm: https://wasmcloud.com/ https://wasmcloud.com/ A lot of those are powered by wasmtime or WasmEdge. If you’re wanting to be able to just pull down a random app and run it as wasm, that’s inherently harder with wasm, because you have to recompile, and amazing compiling stuff is always harder than it should be. For example I compiled jq to wasm to other day, so you dont have to worry (as much) about the CVEs that was issued recently. https://github.com/rockwotj/jq-wasi https://github.com/rockwotj/jq-wasi

4 ms·

I think the wasm C API is not going to live up to the promise. To actually use high performance features you need many additions to that API that most implement

by rockwotj 3y ago

cornstalks 3y ago
Yeah and wasm-c-api has stalled (they still don’t support v128, for example). I’m currently exploring starting an unsanctioned v2 wasm-c-api that aims to be feature complete and hopefully more performance focused.
- rockwotj 3y ago
  Would be super interested in this if you explore this more! Feel free to reach out (contact info linked from my bio) if you’re interested in collaborating.
kelp 3y ago
I'd been hoping projects like wasmtime could end up looking like a Docker alternative for server side things. Do you think that's unlikely to pan out without a lot more work that doesn't seem to be happening?
- rockwotj 3y ago
  Oh it’s certainly looking like that IMO depending on your use case for docker You can run wasm in k8s: https://krustlet.dev/ https://krustlet.dev/ Docker itself can run wasm: https://wasmlabs.dev/articles/docker-without-containers/ https://wasmlabs.dev/articles/docker-without-containers/ There are a few serverless runtimes based on wasm: https://wasmcloud.com/ https://wasmcloud.com/ A lot of those are powered by wasmtime or WasmEdge. If you’re wanting to be able to just pull down a random app and run it as wasm, that’s inherently harder with wasm, because you have to recompile, and amazing compiling stuff is always harder than it should be. For example I compiled jq to wasm to other day, so you dont have to worry (as much) about the CVEs that was issued recently. https://github.com/rockwotj/jq-wasi https://github.com/rockwotj/jq-wasi