undefined | Better HN

0 pointsflohofwoe1y ago0 comments

The only situation I can think of is a plugin system for native applications, where 'WASM DLLs' would solve a lot of issues compared to native DLLs.

But those WASM plugins would be self-contained and wouldn't need to dynamically load other WASM 'DLLs', so that situation is trivial even without the WASM Component Model thingie (which I also think is massively overengineered and kinda pointless - at least from my PoV, maybe other people have different requirements though).

0 comments

nilslice1y ago

this is exactly what we created Extism[0] and XTP[1] for!

[0]: https://extism.org [1]: https://getxtp.com

XTP is the first (afaik) platform of its kind meant to enable an app to open up parts of its codebase for authorized outside developers to “push” wasm plugin code extensions directly into the app dynamically.

We created a full testing and simulation suite so the embedding app can ensure the wasm plugin code does what it’s supposed to do before the app loads it.

I believe this is an approach to integration/customization that exceeds the capabilities of Webhooks and HTTP APIs.

j / k navigate · click thread line to collapse