Over the past few years, we’ve been working to bring graphics to WebAssembly through wasi:webgpu , wasi:surface , wasi:frame-buffer , and wasi:graphics-context . Through this process, it has become clear that the long-term stability goals of the core WASI subgroup and our needs for rapid iteration on UI interfaces are incompatible. WASI aims for decade-long architectural stability. In contrast, interfaces like wasi:surface still require significant evolution. As the Wasm Component Model matures, we see a healthy shift toward projects building distinct ecosystems outside the official WASI namespace — such as the cloud-native wasmcloud:secrets , wasmcloud:messaging and wasmcloud:postgres interfaces developed by CNCF wasmCloud . Think of WASI as an operating system's standard library (handling low-level basics like time and filesystem), while specialized domains like graphics and database drivers belong in user-space libraries.…