W3C tech: "Why Wasm is the future of cloud-native app development" at TechTarget "Wasm has evolved to expand support well beyond the web browser. Developers and organizations are now looking to adopt Wasm on the server side"
@w3c funny, this is exactly what happened with Java! No-one any longer uses it in the browser, but server-side, where architecture agnosticism is largely irrelevant, it's everywhere.
@w3c@w3c.social And even for other very interesting use-cases, not only server-side.
Here it is used to build a "bridge" between compiled Go code, which is shared as a Wasm module that is then re-used to make a Python library to call that (complex) code. See: https://github.com/sfomuseum/py-edtf
