I Built a WebAssembly Runtime in 5 Days
tingouw.com
I Built a WebAssembly Runtime in 5 Days
1–7 of 7 posts
Re: I Built a WebAssembly Runtime in 5 Days
#2If they built a WASM runtime, why do they keep on talking about using wasmtime, which is a WASM runtime.
Re: I Built a WebAssembly Runtime in 5 Days
#3I appreciate the write up.
It comes off very much as a summary of days of vibe-coding from the AI itself, but it's still nice to see the condensed decisions, approach and frankly the whole concept of embedding a wasm runtime.
Re: I Built a WebAssembly Runtime in 5 Days
#4If they built a WASM runtime, why do they keep on talking about using wasmtime, which is a WASM runtime.
Yeah they phrase it more honestly on the actual GitHub repo as a WASM execution platform which makes more sense
Re: I Built a WebAssembly Runtime in 5 Days
#5I would treat bwrap processes as single-use across tenants, since host-side state (allocator, FDs, namespace bits) accumulates and you can not really prove it clean.
Re: I Built a WebAssembly Runtime in 5 Days
#6“I got an LLM to write a summary of the work it did while I occasionally checked in on Cursor.”
I’m getting so tired of these posts. Why waste our time?
Re: I Built a WebAssembly Runtime in 5 Days
#7“I got an LLM to write a summary of the work it did while I occasionally checked in on Cursor.” I’m getting so tired of these posts. Why waste our time?
We need a button for [I carefully read and evaluated this post (I kid, I asked an LLM to summarize it for me)]".
This way, we could return the same level of effort. Most of these vibe coded tools will gather dust almost immediately, such a monumental waste of resources.