Remix.run Logo
DanielHB 2 hours ago

Use cases I am more excited about:

1) Replace webhooks in web apps with wasm binaries provided by the customer, but that run in the web app servers.

2) Safer plugin system for professional software (plugins for photoshop, plugins for IDEs, etc)

3) Safer mod system for games and server-side mods that run on the game-maker server.

bzzzt 2 hours ago | parent | next [-]

We had that in the 90's with Java. Why would this approach succeed today?

simonw an hour ago | parent [-]

Why wouldn't it? It's a different technology stack, developed with the benefit of decades of additional experience running hostile code on the web.

pjmlp 25 minutes ago | parent [-]

You mean like the CLR?

Kind of strange that such experience still allows for WASM to be the target of C and C++ compilers, and there is no bounds checking support inside linear memory regions.

crabmusket 2 hours ago | parent | prev | next [-]

Check out https://extism.org, it is built for those kinds of use cases. However I think WASI and components could enhance it.

DanielHB 12 minutes ago | parent [-]

sorry I meant "most excited about", WASI and components should be useful for the usecases I mentioned too.

For example a SaaS services that accepts WASM plugins could provide a WASI that lets the plugin write to a object-store filesystem (like AWS S3) provided by the SaaS owner.

tuananh 2 hours ago | parent | prev [-]

i had this same vision when i created hyper-mcp with modular plugin system via WASM plugins. Too bad, the community moves on from MCP to CLI with coding agent

https://github.com/hyper-mcp-rs/hyper-mcp