<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JavaScript on Osmond van Hemert</title><link>https://osmondvanhemert.nl/tags/javascript/</link><description>Recent content in JavaScript on Osmond van Hemert</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© Osmond van Hemert. All rights reserved.</copyright><lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://osmondvanhemert.nl/tags/javascript/index.xml" rel="self" type="application/rss+xml"/><item><title>Deno 2.3 and the Runtime Wars — Is Server-Side JavaScript Finally Settling?</title><link>https://osmondvanhemert.nl/posts/260416-deno-2-3-runtime-wars/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://osmondvanhemert.nl/posts/260416-deno-2-3-runtime-wars/</guid><description>Deno 2.3 brings workspace support and improved Node compatibility. With Bun maturing and Node.js evolving, the JavaScript runtime landscape is reaching an interesting equilibrium.</description></item><item><title>The Node.js Renaissance — Deno 2, Bun, and the Evolving JavaScript Runtime Landscape</title><link>https://osmondvanhemert.nl/posts/260101-javascript-runtime-landscape-2026/</link><pubDate>Thu, 01 Jan 2026 00:00:00 +0000</pubDate><guid>https://osmondvanhemert.nl/posts/260101-javascript-runtime-landscape-2026/</guid><description>As we enter 2026, the JavaScript runtime ecosystem is more competitive and innovative than ever. Here&amp;rsquo;s where things stand.</description></item><item><title>Deno 2.5 and the Maturing JavaScript Runtime Wars</title><link>https://osmondvanhemert.nl/posts/250626-deno-25-javascript-runtime-wars/</link><pubDate>Thu, 26 Jun 2025 00:00:00 +0000</pubDate><guid>https://osmondvanhemert.nl/posts/250626-deno-25-javascript-runtime-wars/</guid><description>Deno 2.5 brings improved Node.js compatibility and workspace support, signaling that the JavaScript runtime competition is driving real innovation.</description></item><item><title>The JavaScript Runtime Wars — Bun, Deno, and Node.js in 2024</title><link>https://osmondvanhemert.nl/posts/240314-javascript-runtime-wars-bun-deno-node/</link><pubDate>Thu, 14 Mar 2024 00:00:00 +0000</pubDate><guid>https://osmondvanhemert.nl/posts/240314-javascript-runtime-wars-bun-deno-node/</guid><description>With Bun 1.0 maturing, Deno pushing Node compatibility, and Node.js evolving faster than ever, the JavaScript runtime landscape is more interesting than it&amp;rsquo;s been in years.</description></item><item><title>Bun Enters the Ring — A New JavaScript Runtime Challenges Node</title><link>https://osmondvanhemert.nl/posts/220728-bun-javascript-runtime-shakes-up-ecosystem/</link><pubDate>Thu, 28 Jul 2022 00:00:00 +0000</pubDate><guid>https://osmondvanhemert.nl/posts/220728-bun-javascript-runtime-shakes-up-ecosystem/</guid><description>Bun, a new JavaScript runtime built on JavaScriptCore and written in Zig, is making waves with extraordinary benchmark numbers. Is it the Node.js challenger we&amp;rsquo;ve been waiting for?</description></item><item><title>Deno 1.0 — Ryan Dahl's Do-Over for Server-Side JavaScript</title><link>https://osmondvanhemert.nl/posts/200514-deno-1-0-release/</link><pubDate>Thu, 14 May 2020 00:00:00 +0000</pubDate><guid>https://osmondvanhemert.nl/posts/200514-deno-1-0-release/</guid><description>Deno 1.0 launches with TypeScript support, a security-first permissions model, and a clean break from Node.js conventions — but can it find its niche?</description></item><item><title>GitHub Acquires npm — What This Means for the JavaScript Ecosystem</title><link>https://osmondvanhemert.nl/posts/200319-github-acquires-npm/</link><pubDate>Thu, 19 Mar 2020 00:00:00 +0000</pubDate><guid>https://osmondvanhemert.nl/posts/200319-github-acquires-npm/</guid><description>GitHub&amp;rsquo;s acquisition of npm consolidates the JavaScript ecosystem&amp;rsquo;s most critical infrastructure under one roof. Here&amp;rsquo;s why that matters — and what could go wrong.</description></item></channel></rss>