WebAssembly or Wasm for brevity is a Web-optimized executable software format designed to give programmers the greatest possible flexibility. Wasm binary modules can be compiled once and then safely run anywhere alone or embedded in other applications. In practice Wasm needs at least three key components to keep that promise. Two of them already presented in this series are the WebAssembly System Interface WASI and Wasm Interface Types.

WASI gives Wasm modules standard language-independent ways to interact with any host environment in which they may land. The Interface Types instead are equally standardized definitions but for all kinds of software variables. By using them Wasm modules can pass complex data structures to each other without risking corrupting them even if they were written by independent programmers in very different source languages. The other main piece of this puzzle is called module linking. This is what allows distinct binary files to interact directly for example using each others functions as if they were both written as different sections of the same source code and then compiled together.


Read Full Post

News Link: https://www.linux.com/news/how-and-why-to-link-webassembly-modules/.
RSS Link: https://www.linux.com/feed/.

Linux Chatter is a news aggregator service that curates some of the best Linux, Cloud, Technical Guides, Hardware and Security news. We display just enough content from the original post to spark your interest. If you like the topic, then click on the 'read full post' button to visit the author's website. Use Linux Chatter to find content from amazing authors!

Note: The content provided has been modified and is not displayed as intended by the author. Any trademarks, copyrights and rights remain with the source.

Disclaimer: Linux Chatter sources content from RSS feeds and personal content submissions. The views and opinions expressed in these articles are those of the authors and do not necessarily reflect those of Linux Chatter.