<story><title>Hello wasm-pack</title><url>https://hacks.mozilla.org/2018/04/hello-wasm-pack/</url></story><parent_chain></parent_chain><comment><author>axefrog</author><text>Does anyone have a good sense of the current performance impact of crossing the boundary between JS and WASM? I&amp;#x27;ve often thought it&amp;#x27;d be great to be able to expose high-performance data structures (and other infrastructure-level stuff) via WASM and then make use of them from JavaScript, but I seem to recall that the interop performance cost is currently too high to make it worth doing, which leaves WASM mainly only useful for long-running tasks, such as game engines, expensive graph layout algorithms and so forth.&lt;p&gt;&lt;i&gt;&lt;/i&gt;Edit:&lt;i&gt;&lt;/i&gt;
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hacks.mozilla.org&amp;#x2F;2018&amp;#x2F;04&amp;#x2F;javascript-to-rust-and-back-again-a-wasm-bindgen-tale&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hacks.mozilla.org&amp;#x2F;2018&amp;#x2F;04&amp;#x2F;javascript-to-rust-and-bac...&lt;/a&gt;&lt;p&gt;&amp;gt; &amp;quot;The wasm-bindgen code generation has been designed with the future host bindings proposal in mind from day 1. &lt;i&gt;As soon as that’s a feature available in WebAssembly&lt;/i&gt;, we’ll be able to directly invoke imported functions without any of wasm-bindgen‘s JS shims. Furthermore, this will allow JS engines to aggressively optimize WebAssembly manipulating the DOM as invocations are well-typed and no longer need the argument validation checks that calls from JS need. At that point wasm-bindgen will not only make it easy to work with richer types like strings, but it will also provide best-in-class DOM manipulation performance.&amp;quot;</text></comment>
<story><title>Hello wasm-pack</title><url>https://hacks.mozilla.org/2018/04/hello-wasm-pack/</url></story><parent_chain></parent_chain><comment><author>mpolichette</author><text>I cant help but think of the post about stealing password credentials from the site you build by surreptitiously inserting extra code into the published NPM package.  Except wasm packages seem like they&amp;#x27;d be even harder to detect.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hackernoon.com&amp;#x2F;im-harvesting-credit-card-numbers-and-passwords-from-your-site-here-s-how-9a8cb347c5b5&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hackernoon.com&amp;#x2F;im-harvesting-credit-card-numbers-and...&lt;/a&gt;</text></comment>