Remix clone Hacker News

After delving into this, it seems Wasmer tried, but as they weren't standards compliant, adoption/ecosystem support never followed.

The Bytecode alliance is taking their time stabilizing wasi. wasip2 which is needed for the wasi-http realm this relies on has only really existed for a few months as a stable Rust target, and still misses a lot of the really cool features that will come with wasip3 like full async support.

I suspect Cloud providers will adopt wasi after 1.0, but that is likely years away. I don't think wasi-http will change much before then so now is the time to start building with it.

▲

syrusakbary 9 hours ago | parent | next [-]

> After delving into this, it seems Wasmer tried, but as they weren't standards compliant, adoption/ecosystem support never followed.

You may be surprised by how much WASIX is being adopted by the ecosystem! Aiming it to be full POSIX compliant has proven incredibly powerful, as there's no need for waiting for other entities to reinvent what already works in the POSIX (macOS, Linux, ...) :)

▲

alexboehm 9 hours ago | parent [-]

I'm not discounting WASIX or what you guys are doing I'd love to just use wasm today for everything instead of waiting, I started this project by trying to use WASIX, I just found it quite difficult to actually develop for as many of the essential rust crates, seemed reluctant to merge your changes, and having to use dependency versions from a year ago with patches is very frustrating.

	▲	syrusakbary 4 hours ago \| parent [-]
		Fair! We have already plans to solve the patching issue you commented... stay tuned!

▲

sshine 10 hours ago | parent | prev [-]

So happy to see wasi-http become stable.