Filling a Registry-Shaped Hole in the Wasm Component Ecosystem by D. Macovei / O. Spencer @ Wasm I/O

Wasm I/O 2024 / 14-15 March, Barcelona
Speakers: Danny Macovei and Oscar Spencer
Slides: docs.google.co...
Repo: github.com/mac...
Wasm components are here and soon to be everywhere. This talk introduces the latest in developer tools for composing, publishing and deploying components. We will introduce the WebAssembly Registry (Warg) protocol and then use it to develop, publish, and deploy.
Today, there are developer library registries (on npm, RubyGems, Crates.io, etc.) and there are deployment artifact registries (OCI, DockerHub, etc.). Wasm component registries blur this distinction. A Wasm component can be imported and used as a library in your programming language, or the same component can be easily composed with a little configuration into a new component that is a complete deployment artifact. This talk demonstrates how Wasm registries make it seamless to use components as libraries or deploy them as services.

[@capability-snob]

Explicit arguments in module instantiation is so much nicer than SBOM. Capabilities are the best way to do modules! You can tell what uses dangerous features, where you need to focus your security audit, etc. Well done.

[@tenthlegionstudios1343]

Great to hear that you have handles and can share memory from one module across all components. I am very interested in this but can't find any info on this.
Please share where you can find this! I know youtube doesn't let you share links - unless the author approves it. I am very interested in this topic.

[@admalledd]

Most of the shared memory stuff is under the WAM Threads proposals, since many of the core issues with shared memory also live when doing threads. There are some methods to do this today (re-exporting module internal memory for example) but are under-defined compared to most stuff.