<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #wasm</title>
    <link>/tags/wasm/</link>
    <description>Recent bookmarks tagged #wasm</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:48 +0000</lastBuildDate>
    <item>
      <title>Firefox in WebAssembly</title>
      <link>https://developer.puter.com/labs/firefox-wasm/</link>
      <description>he Gecko engine compiled to WebAssembly.&#xA;The real Firefox interface, rendering entirely inside this browser tab.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #firefox #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 16 Jul 2026 03:13:29 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38649</guid>
      <category>firefox</category>
      <category>wasm</category>
      <category>webdev</category>
    </item>
    <item>
      <title>HeyPuter/firefox-wasm: 🦊 Firefox in WebAssembly</title>
      <link>https://github.com/HeyPuter/firefox-wasm</link>
      <description>🦊 Firefox in WebAssembly&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #firefox #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 16 Jul 2026 03:12:49 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38648</guid>
      <category>firefox</category>
      <category>wasm</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/068585e48730676c908b59306e250f88.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>MikeSchirtzinger/silent-notetaker: Private, on-device AI meeting notetaker that runs entirely in your browser — live transcription, speaker ID, and note extraction with no audio leaving your machine (WebGPU + WASM).</title>
      <link>https://github.com/MikeSchirtzinger/silent-notetaker?utm_campaign=ai-tinkerers-columbus-june-meetup&amp;utm_content=link1&amp;utm_medium=ai-tinkerers&amp;utm_source=columbus</link>
      <description>Private, on-device AI meeting notetaker that runs entirely in your browser — live transcription, speaker ID, and note extraction with no audio leaving your machine (WebGPU + WASM).&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #notes #tools #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Mon, 15 Jun 2026 22:36:39 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38579</guid>
      <category>notes</category>
      <category>tools</category>
      <category>wasm</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/69f8553d9af078a67e422f990f2a90f4.png" type="image/png"></enclosure>
    </item>
    <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>
    <item>
      <title>LinuxOnTab — Real Linux in your browser. No install, no server, no Docker.</title>
      <link>https://linuxontab.com/</link>
      <description>LinuxOnTab boots a real x86 Linux kernel and Alpine userland inside your browser using WebAssembly and the v86 emulator. A zero-install, local-first, in-browser Linux terminal — a lightweight Docker alternative for instant sandboxes, teaching, demos, and disposable shells.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #linux #nifty #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 06 May 2026 12:36:15 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38524</guid>
      <category>linux</category>
      <category>nifty</category>
      <category>wasm</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/8889c4430da51ea2e5167333d8f5b868.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Password Protecting Static Site Content with WASM</title>
      <link>https://al9000.com/rust/wasm/static-site-file-decryption/</link>
      <description>I use static site generators for my sites. I call out to external APIs to do anything dynamic. The exception is password protection. I&#39;d always thought that needed to be done dynamically on a site&#39;s host server. I realized with WASM that&#39;s not the case. Files can be encrypted and served statically with a WASM process providing decryption directly on the front end.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #metablogging #security #ssg #static #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 07 Apr 2026 00:03:23 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38451</guid>
      <category>metablogging</category>
      <category>security</category>
      <category>ssg</category>
      <category>static</category>
      <category>wasm</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/b6504d71db92fffeba1641c8c3b22c58.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>Irreducible</title>
      <link>https://irreducible.io/blog/porting-doom-to-wasm/</link>
      <description>Anyways… I’ve reached the point that my VM is fully compliant with version 2.0 of the WebAssembly core specification, and I need a large program to stress test it with. The obvious choice for this sort of thing is a DOOM port. For those unaware, DOOM runs on just about every computing environment under the sun. For every calculator, satellite, or turing-complete system, there’s likely a software engineer theorizing about how to get DOOM running on it.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #doom #vm #wasm&lt;/p&gt;</description>
      <pubDate>Mon, 26 Jan 2026 22:42:09 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38239</guid>
      <category>doom</category>
      <category>vm</category>
      <category>wasm</category>
    </item>
    <item>
      <title>EmNudge/watlings: Learn WebAssembly by writing small programs!</title>
      <link>https://github.com/EmNudge/watlings</link>
      <description>Learn the WebAssembly Text Format&#xA;by fixing a bunch of small programs!&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 09 Jan 2026 22:40:13 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38185</guid>
      <category>dev</category>
      <category>wasm</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/d6f18e83df23e478ff03354ac5a251de.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>What Happened To WebAssembly</title>
      <link>https://emnudge.dev/blog/what-happened-to-webassembly/</link>
      <description>On every WebAssembly discussion, there is inevitably one comment (often near the top) asking what happened.&#xA;&#xA;It seems to have been advertised as a world-changing advancement. Was it just oversold? Was it another JVM applet scenario, doomed to fail?&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #tech #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 09 Jan 2026 18:15:47 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38184</guid>
      <category>tech</category>
      <category>wasm</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Polyglot AI Agents: WebAssembly Meets the JVM</title>
      <link>https://blog.mozilla.ai/polyglot-ai-agents-webassembly-meets-the-java-virtual-machine-jvm/?utm_source=Social%20(RB)</link>
      <description>In previous posts, Davide Eynard demonstrated how to run agentic frameworks in the browser, while Baris Guler showed how to extend them with in-browser inference and support for multiple programming languages. In this post, we leverage the JVM&#39;s polyglot capabilities to create a self-contained, enterprise-optimized server-side blueprint that combines the performance benefits of WebAssembly with the reliability and maturity of Java&#39;s ecosystem.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #java #jvm #llm #wasm&lt;/p&gt;</description>
      <pubDate>Sun, 14 Dec 2025 01:47:52 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38110</guid>
      <category>ai</category>
      <category>java</category>
      <category>jvm</category>
      <category>llm</category>
      <category>wasm</category>
      <enclosure url="https://links.lmorchard.com/static/efcfe6fcc7a3b32cb0f393bb63298119.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Introducing Wassette: WebAssembly-based tools for AI agents - Microsoft Open Source Blog</title>
      <link>https://opensource.microsoft.com/blog/2025/08/06/introducing-wassette-webassembly-based-tools-for-ai-agents/</link>
      <description>The Azure Core Upstream team is happy to introduce Wassette: a security-oriented runtime that runs WebAssembly Components via Model Context Protocol (MCP). Wassette allows agents to autonomously fetch WebAssembly (Wasm) Components from Open Container Initiative (OCI) registries and execute them as needed. It’s built on the Wasmtime runtime, offering secure sandboxing on par with modern browser engines. To enhance security, Wassette includes a fine-grained, deny-by-default permission system, allowing interactive control over access to system resources.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #llms #mcp #wasm&lt;/p&gt;</description>
      <pubDate>Tue, 12 Aug 2025 17:45:26 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29381</guid>
      <category>ai</category>
      <category>llms</category>
      <category>mcp</category>
      <category>wasm</category>
      <enclosure url="https://links.lmorchard.com/static/da656fffa43dc218134c3a2fdfa7af40.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Porting Terraria and Celeste to WebAssembly</title>
      <link>https://velzie.rip/blog/celeste-wasm</link>
      <description>As much as I can justify it, this project is probably going to be useless to most people. Not many people are seriously going to play all of celeste or terraria in the browser, and the novel things we did discover along the way are probably too niche to be of any help to anyone else.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #celeste #gamedev #gaming #terraria #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Sun, 01 Jun 2025 18:34:14 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29495</guid>
      <category>celeste</category>
      <category>gamedev</category>
      <category>gaming</category>
      <category>terraria</category>
      <category>wasm</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Why I use WebAssembly - nasso</title>
      <link>https://nasso.dev/blog/why-i-use-wasm</link>
      <description>Finally, we reach the juicy part. My favorite way to use WebAssembly is as a way to share code between platforms. Write the core logic of your application in Ru… a language that can easily compile to native code and WebAssembly 😊. In this architecture, most of your code is shared between the “native” and the “web” variants of your app. Maybe some platform-specific features will need to be turned on or off with compile-time flags, but if you’re building a cross-platform app, you are probably already dealing with different code paths for different platforms anyway. With WebAssembly, the web just becomes another platform to target!&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #rust #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 15 May 2025 05:11:16 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29512</guid>
      <category>rust</category>
      <category>wasm</category>
      <category>webdev</category>
    </item>
    <item>
      <title>PGlite</title>
      <link>https://pglite.dev/</link>
      <description>Run a full Postgres database locally in WASM with reactivity and live sync.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #postgres #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 09 May 2025 05:35:23 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29532</guid>
      <category>postgres</category>
      <category>wasm</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/e498bc99a605971371254be2b370868a.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>MicroW8</title>
      <link>https://exoticorn.github.io/microw8/</link>
      <description>MicroW8 is a WebAssembly based fantasy console inspired by the likes of TIC-80, WASM-4 and PICO-8.&#xD;&#xA;&#xD;&#xA;The initial motivation behind MicroW8 was to explore whether there was a way to make WebAssembly viable for size-coding. (Size coding being the art of creating tiny (often &lt;= 256 bytes) graphical effects and games.) The available examples so far are all in this space, however, I very carefully made sure that all design decisions make sense from the point of view of bigger projects as well.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #fantasyconsoles #microw8 #retro #wasm #webdev&lt;/p&gt;</description>
      <pubDate>Sun, 20 Apr 2025 17:35:14 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29569</guid>
      <category>fantasyconsoles</category>
      <category>microw8</category>
      <category>retro</category>
      <category>wasm</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
