Bun, a JavaScript runtime built with Zig, can execute TypeScript directly and includes built‑in TS‑to‑JS tooling, but Zig’s strict no‑AI contribution rule clashes with Anthropic’s acquisition of Bun, prompting the creator to release a Zig‑to‑Rust migration guide that admits the rewrite is still experimental.
This article examines how Bun’s ultra‑fast package manager, integrated JavaScript runtime, native test runner, and built‑in database/S3 client together deliver a faster, lighter, and more streamlined development experience compared to traditional Node.js and npm workflows.
This article compares Node.js and Deno across three rounds—security, performance, and developer experience—showing code examples, benchmark results, and practical trade‑offs to help developers decide which JavaScript runtime best fits their projects.
Bun 1.2 delivers its biggest upgrade yet, boosting Node.js compatibility above 90% for core modules, adding built‑in PostgreSQL and native S3 support that outperforms the AWS SDK, switching to a readable lock file for faster installs, enhancing testing tools, and improving HTTP/2, filesystem, JSON and Windows performance while targeting remaining compatibility gaps.
Version 1.2 of the Bun runtime introduces five significant enhancements—including improved Node.js compatibility, HTML import that replaces the entire frontend toolchain, native S3 object handling, a fast Promise‑based Postgres driver, and a text‑based lock file—positioning Bun as a comprehensive, cloud‑first JavaScript ecosystem.
Deno 1.26, released on September 29, introduces Node.js compatibility layer enhancements, updated readable‑stream implementation, new APIs like Writable.toWeb() and Readable.toWeb(), performance improvements, added CacheWeb support, a new –allow‑sys permission flag, and bundles TypeScript 4.8, positioning Deno as a faster, more compatible JavaScript runtime.
Deno has achieved 4.1 million downloads on GitHub, 250,000 monthly active users, plans to support most npm packages within three months, and aims to become the fastest JavaScript runtime with an upcoming HTTP server touted as the fastest JavaScript web server ever.
The recent Deno announcement reveals native npm package support, a faster HTTP server, and fierce competition from Bun, highlighting performance benchmarks, community reactions, and the ongoing race to become the fastest JavaScript runtime for backend development.
Over three years, Shopee evolved its React Native architecture from a single‑bundle, centralized model to a fully decentralized system where each team independently develops, builds, and releases code, using an isolated JavaScript runtime and a self‑built Code Push Platform that manages permissions, incremental updates, grayscale releases, and migration of legacy plugins without disrupting ongoing business.
This article explains what Deno is, its origins and motivations, compares it with Node.js, describes its Rust‑based architecture, security model, built‑in tools, TypeScript and WebAssembly support, and provides step‑by‑step examples for installation, HTTP requests, remote imports, and building simple services.
This article introduces Node.js by covering its origins, core architecture, key features such as event‑driven non‑blocking I/O, and the scenarios where it excels, helping readers decide when and why to choose Node.js for backend development.
This article explains Node.js architecture, showing how JavaScript code interacts with the operating system via C/C++ bindings, clarifies the single‑threaded model backed by a thread pool, and details the libuv‑based event loop that enables high‑concurrency non‑blocking I/O.
