#wasi — Public Fediverse posts

#WASM / #WASI based #plugin architectures vs #AGPL?

I assume this is valid, but #IANAL and unsure if it is indeed the case:

- If the core system is AGPL-licensed and integrates a Wasm WASI runtime.
- Then 3rd-party WASI Components can have different licenses.
- Esp. when they are downloaded and installed at run-time.

OTOH perhaps not.. and it depends on who designed the #WIT #RPC interface, and what its #license is.

#Socialcoding topic (2024, all fedi links rotted)..

https://discuss.coding.social/t/sx-licensing-of-plugin-architecture-vs-agpl/506

When I use cargo component new to build a CLI component for Rust/Wasm/Wit, the cargo component build step will automatically translate a main function to .e.g. wasi:cli/run or println! statements to the according stream functions from the wasi world. With wasm-tools component wit I can even inspect a generated with world, though none was supplied. I would llike to know more about the magic involved. Is that documented somewhere, is this something carfgo component does, or is it coming from wit-bindgen? Any help or pointers appreciated.

#rust #wasm #wit #wasi #wasip2 #cargo #componentmodel