<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #asmjs</title>
    <link>/tags/asmjs/</link>
    <description>Recent bookmarks tagged #asmjs</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:55 +0000</lastBuildDate>
    <item>
      <title>Saying goodbye to asm.js | SpiderMonkey JavaScript/WebAssembly Engine</title>
      <link>https://spidermonkey.dev/blog/2026/05/20/saying-goodbye-to-asmjs.html</link>
      <description>asm.js was Mozilla’s response to the question posed by NaCl and PNaCl: how can the web run code at native speeds?&#xA;&#xA;The idea was clever: pick a strict, statically-typed subset of JavaScript that an engine could recognize on the fly and compile down to native code. We could get performance similar to NaCl/PNaCl and still have code live inside web content and use web API’s (no separate sandbox, IPC, or alternative API’s).&#xA;&#xA;asm.js shipped in Firefox 22 back in 2013 and was a success. It let projects like Unity and Unreal ship C/C++ codebases to the web for the first time, using just standard web technologies. The Epic Citadel demo was ported to the web in just four days. It was a landmark achievement, and a fond memory for the original asm.js team.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #asmjs #firefox #javascript #mozilla #wasm&lt;/p&gt;</description>
      <pubDate>Wed, 20 May 2026 16:42:18 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38549</guid>
      <category>asmjs</category>
      <category>firefox</category>
      <category>javascript</category>
      <category>mozilla</category>
      <category>wasm</category>
      <enclosure url="https://links.lmorchard.com/static/9add03218fb7e8c3ba4ba2f9884a0abc.png" type="image/png"></enclosure>
    </item>
  </channel>
</rss>
