tl;dr: A caech-able method for including other programming language sourcecode which is then interpreted or compiled clientside.<p>--------------<p>One thing that would be interesting about the concept of web assembly, is if this allows for running websites where the source code is in a textual format that is interpreted or compiled from any arbitrary language.<p>Take for instance the humble<p><pre><code> <script type="text/javascript"></script>
</code></pre>
The issue with including other standards would be the need to bake support for the language into it.<p>## External Link to Interpreter/Compiler in script tag<p>What if the script tag also supports a reference to a web assembly binary that is tasked with reading the source code and compiling it to web assembly?<p><pre><code> <script interpreter="dartlang.org/compiler.wasm" type="text/dart"></script>
<script compiler="tcc.org/tcc.wasm" type="text/C"></script>
</code></pre>
The compiler reference runs a bit like a 'preprocessor' converting C code into wasm. While the interpreter mode, would run the interpreter on top of the web assembly virtual machine. Having it be a separate referenced link, would provide opportunity for informing the browser to cache the compiler/interpreter for future usage (Which is a good thing if its a popular language).<p>## Package Repository approach to Interpreter/Compiler<p>The other approach besides linking to an external compiler/interpreter. Is to maybe have a "package manager" approach this code. Which means all the major browser would link to a common package repository of such interpreter/compiler, along with various versioning. This would also allow for implicit imports based on the `type` field of the script.<p><pre><code> <script type="text/javascript"></script>
<script language="python_V3.x" type="text/python"></script></code></pre>