[mrmagoo17]

That's a really cool implementation! I hope I'll have some time soon to have a peek at the code. I am honestly a bit surprised to see that none of the major cloud providers are even thinking to leverage WASM and WASI for serverless...

[Imustaskforhelp]

Cloudflare workers can do wasm and js.

I haven't tried with wasm personally because well, it has a limit of 25 mb and I am not sure but last time I read somewhere in their forums about some guy wishing to run golang, it had the issue that wasm could only be 1-2mb and golang's most basic example had it taken 1-2mb so they can't cook anything good.

Of course I can be wrong & I am just too lazy to search that article to remember the facts again.

[Imustaskforhelp]

Cloudflare is literally magic with typescript. I swear, people like to give me that cloudflare example of gambling and show the time where their sales team messed up so hard but If we read that article, I think I can agree with Cloudflare because they were a gambling site... my gripe is that cloudflare could've been more professional, but hey mistakes happen , I genuinely hope that Cloudflare has moved on, Since if I ever create any website, any service whatever, Its most likely going to be on Cloudflare and I just hope that I don't get messed up like that guy.

And also one key thing to note is you should probably not keep the domain itself in cloudflare if you are thaat paranoid and write something in hono if you really want portability (maybe its overkill??) and if you really get messed up like the gambling blog guy then you can easily switch away...

Still ITS way too unlikely to happen I guess.

[phickey]

Azure has shipped Spin as an experiment https://learn.microsoft.com/en-us/azure/aks/use-wasi-node-po... and is investing in Wasmtime and WASI https://opensource.microsoft.com/blog/2025/03/26/hyperlight-... (One author, Yosh, is the co-chair of WASI standards subgroup)

This platform is also based on wasmtime and wasmtime's wasi-http implementation, which I authored, so I'm really proud to see it reused here!

One more plug: I've been working on https://github.com/yoshuawuyts/wstd/ with Yosh and Dan Gohman (creator of WASI) as a nice way to write wasi-http guests in Rust.

[case]

Check out Fastly’s WASM-powered Compute platform:

https://www.fastly.com/documentation/guides/compute/

(I work there)

[alexboehm]

I have been playing with it, it's very cool to be able to run anywhere. Do you have plans to implement wasi-http? One of my concerns is the free tier only offers Compute as a trial, and $50 is pretty steep for a hobby project, are there plans to add Compute usage to the free tier?

[alexboehm]

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]

> 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]

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]

Fair! We have already plans to solve the patching issue you commented... stay tuned!

[sshine]

So happy to see wasi-http become stable.

[sitkack]

They don't want to kill their Golden Geese.