yosh

@yosh@toot.yosh.is

Better things are not only possible; they're within reach.

Concurrent Computing ←
Programming Language Design ←
Rust and WebAssembly at Microsoft ←

u(๑╹ᆺ╹)

This profile is from a federated server and may be incomplete. Browse more on the original instance.

yosh, 14 hours ago to random

oh did I mention I'm going to start streaming again? currently still working out the logistics, but most likely starting again sometime next week - together with a colleague.

I was just moving things around in my office, making sure that e.g. the lighting will work out okay for that. here's a very dramatic first test shot

reply

expand (1)

collapse (1)

report

activity

copy /kbin url

copy original url

open original url

Loading...

yosh, 5 days ago to random

LRT: Async in WASI 0.3 externalizes the runtime entirely, making it possible to provide first-class async at the ABI level.

This means there is no runtime to thread through the program: the host responsible for running the Wasm program is the reactor.

All you do at the boundaries of your program is say things like: "this is a stream of values" or "this is a future", and the host + bindings generator will handle it correctly. This enables compositions of programs to share one runtime.

reply

expand (2)

collapse (2)

report

activity

copy /kbin url

copy original url

open original url

Loading...

+ emattiza

yosh, 5 days ago

What's also neat is that for API abstractions on top of 0.3 syscalls, supporting sync and async requires roughly the same amount of work.

All you have to do is tell the bindings generator you want the async/.await version of the API, and the host just has support for that. Wrapping that in e.g. the Rust stdlib should be no extra work at all, given we had a place to expose the types from.

reply

report

activity

copy /kbin url

copy original url

open original url

Loading...

+ emattiza