Using wasm component model for ultimate extensibilty?

[DougAnderson444]

Related: #983

I mentioned in the PR that I'd open up a discussion on the possibilities that wasm component could offer to what limbo's goals are.

I'm new to limbo, but old to Rust/Wasm. I need limbo to have extensions, and if these extensions are supposed to be runtime loadable like in C-sqlite, then limbo needs a model that supports that too, right?

I'm not 100% sure what it would look like, but what I do know if that wasm components can be composed together to form a bigger component.

So SELECT load_extension('path_to_extension'); would translate into a wasm-to-wasm call to pull the interface in from that extension? Brainstorming here as I haven't quite figured out how that would work, but there's something there.

Anyway I wanted to start the ball rolling and gauge interest.

[penberg]

Hey @DougAnderson444! I am not 100% sure what loadable Wasm components would look like, but it's certainly something I would love to support -- if it makes sense for applications. Note that right now the assumption is that some popular extensions like UUID, for example, will just be bundled so no runtime loading is needed. But I think it's at least interesting to explore what loadable Wasm extensions would look like.