<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Deno on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/deno/</link>
    <description>Recent content in Deno on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 28 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/deno/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Node.js vs Bun vs Deno in 2026: Which JavaScript Runtime Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-28-nodejs-vs-bun-vs-deno-javascript-runtimes-comparison/</link>
      <pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-28-nodejs-vs-bun-vs-deno-javascript-runtimes-comparison/</guid>
      <description>&lt;p&gt;Your CI pipeline spent &lt;strong&gt;47 seconds&lt;/strong&gt; installing dependencies. Your serverless function cold-starts in 800 milliseconds. Your TypeScript build needs a separate step just to strip types. Every one of those costs is set the day you pick a JavaScript runtime — and switching later means rewriting import maps, permission flags, and Dockerfiles that nobody documented. In 2026 the choice is genuinely three-way: &lt;strong&gt;Node.js 24&lt;/strong&gt; (the incumbent, now on its third decade), &lt;strong&gt;Bun&lt;/strong&gt; (the all-in-one speed demon that bundles, transpiles, tests, and installs), and &lt;strong&gt;Deno&lt;/strong&gt; (the security-first runtime built by Node&amp;rsquo;s original creator). This guide compares them with live GitHub data, official install scripts, and production-tested Docker configurations so you can decide in ten minutes, not ten days.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
