<story><title>Clang runs in the browser and compiles C++ to WebAssembly</title><url>https://tbfleming.github.io/cib/</url></story><parent_chain><item><author>tzahola</author><text>Replace “WebAssembly VM” with “JVM” and you will see how it’s already available, and why it won’t catch on.</text></item><item><author>shalabhc</author><text>Next we&amp;#x27;ll get to a webassembly-only VM that will replace the OS. All &amp;#x27;apps&amp;#x27; will run on this VM instead of being native, and most will be cross platform. They&amp;#x27;ll talk to each other via messaging (using Javascript semantics) instead of bytes-over-pipes as they do today. An integrated globally available, namespaced data store API might replace the filesystem. Each app+version will be accessible by a distinct URL. &amp;#x27;My computer&amp;#x27; will finally be fully virtual - a well defined collection of &amp;#x27;apps&amp;#x2F;data&amp;#x27; URLs that materializes wherever I can open one of these webassembly VMs.&lt;p&gt;With this webassembly VM, early bound (precompiled) lower level languages may not have a strong advantage over late bound, dynamic ones, because the compiler is part of the OS layer (as it should be).&lt;p&gt;The world seems to be slowly moving, in a roundabout way, towards the OS-browser idea from Alan Kay.</text></item></parent_chain><comment><author>int_19h</author><text>JVM had to be installed, and it was far from seamless the way OP describes it.&lt;p&gt;The advantage of wasm is that all the people running Chrome today already have it.</text></comment>
<story><title>Clang runs in the browser and compiles C++ to WebAssembly</title><url>https://tbfleming.github.io/cib/</url></story><parent_chain><item><author>tzahola</author><text>Replace “WebAssembly VM” with “JVM” and you will see how it’s already available, and why it won’t catch on.</text></item><item><author>shalabhc</author><text>Next we&amp;#x27;ll get to a webassembly-only VM that will replace the OS. All &amp;#x27;apps&amp;#x27; will run on this VM instead of being native, and most will be cross platform. They&amp;#x27;ll talk to each other via messaging (using Javascript semantics) instead of bytes-over-pipes as they do today. An integrated globally available, namespaced data store API might replace the filesystem. Each app+version will be accessible by a distinct URL. &amp;#x27;My computer&amp;#x27; will finally be fully virtual - a well defined collection of &amp;#x27;apps&amp;#x2F;data&amp;#x27; URLs that materializes wherever I can open one of these webassembly VMs.&lt;p&gt;With this webassembly VM, early bound (precompiled) lower level languages may not have a strong advantage over late bound, dynamic ones, because the compiler is part of the OS layer (as it should be).&lt;p&gt;The world seems to be slowly moving, in a roundabout way, towards the OS-browser idea from Alan Kay.</text></item></parent_chain><comment><author>C14L</author><text>The big difference is that the &amp;quot;Browser VM&amp;quot; has well defined permissions to access resources on the host machine. Just like phone OSes do today. Bluetooth API, Files API, Location API, etc.</text></comment>