Bailey Hayes

> A WASIp2 → WASIp1 adapter This adapter is something many of us want to see and believe is technically feasible. For the concerns around accidental usage of new API's,...

I agree that the wasip1 proposal should remain frozen; the established practice of providing host-specific additional APIs for content to use continues to be the right way to address needs...

My feeling is that we should pursue and support both options as outlined.

For anyone following the stream API's link, it's under the wit folder https://github.com/WebAssembly/wasi-io/blob/main/wit/wasi-io.wit.md

It looks like we brought over the tagged version of the package which is what I'd expect: https://github.com/WebAssembly/wasi-http/blob/v0.2.0/wit/proxy.wit#L5 Then later new changes came onto main that would be really great...

[wasi-clocks](WebAssembly/wasi-clocks) did not have a goal of implementing timezones. It implemented `clock_time_get`. There is a similar libc API `gettimeofday` that is used to surface both the time and timezone. We...

I expect this to largely be solved at the component-model level and not wasi. I expect many apps to depend on the same ICU component as a dependency (https://github.com/unicode-org/icu4x).

I'm interested in your thoughts on surfacing the [Internationalization API Specification](https://tc39.es/ecma402/#datetimeformat-objects) through WASI. I pitched this in a related but simpler case in [239](https://github.com/WebAssembly/WASI/issues/239#issuecomment-1401349448). This doesn't completely solve the ask....

Yes I totally expect different communities to build shared API's and with planned resource handles on WIT definitions, they can pass blobs. proxy-wasm is one example of a community coming...

I am in favor of this proposal. As a separate process question, is there a list of producers that need to be updated? It may help to communicate early with...