---
title: "Deno 1.0: Ryan Dahl's Node.js successor"
description: "Deno 1.0 (May 2020) by Ryan Dahl (Node.js creator): JavaScript/TypeScript runtime in Rust, secure by default, native TypeScript, single binary. Correcting Node.js design mistakes ten years later."
url: "https://www.noze.it/en/insights/deno-1-0/"
lang: "en"
alternate: "https://www.noze.it/insights/deno-1-0/"
published: "2020-05-13"
author: "noze S.r.l."
keywords: "Open Source, Web, R&D, Deno, Ryan Dahl, TypeScript, Runtime, JavaScript, Rust"
---

# Deno 1.0: Ryan Dahl's Node.js successor

Deno 1.0 (May 2020) by Ryan Dahl (Node.js creator): JavaScript/TypeScript runtime in Rust, secure by default, native TypeScript, single binary. Correcting Node.js design mistakes ten years later.

13 May 2020

## “10 things I regret about Node.js”

In **June 2018 Ryan Dahl** — creator of **Node.js** (2009) — presents at JSConf EU a talk that became famous: _“10 Things I Regret About Node.js”_. Criticisms:

1. No native TypeScript
2. Promises arrived late
3. Confusing module system (CommonJS vs ESM)
4. Huge and branching node_modules
5. Overly descriptive package.json
6. Complicated V8 binding
7. No permissions (a module has full filesystem access)
8. GYP and historical build system
9. Non-standard libraries
10. Initial design mistakes

Dahl announces **Deno**, a new runtime solving these critiques. Two years of development; **Deno 1.0** is released on **13 May 2020**. **MIT** licence.

## Key differences from Node.js

- **Native TypeScript** — no Babel, no ts-node: `deno run script.ts` just works
- **Secure by default** — requires explicit flags for permissions: `--allow-net`, `--allow-read`, `--allow-write`, `--allow-env`, `--allow-run`
- **Rust runtime** + V8 — safer and more performant architecture
- **URL imports** — `import { serve } from "https://deno.land/std/http/server.ts"`; no package.json nor node_modules
- **Web Platform API** — `fetch`, `WebSocket`, `Blob`, `crypto.subtle` available in runtime like browser
- **Standard library** unified in `deno.land/std`
- **Testing** and **formatter** and **linter** **built-in**

## Yet Node.js dominates

Despite technical quality, Deno struggles to conquer the Node.js market due to the vast existing **npm ecosystem**: compatibility with packages from the npm registry remains one of the project’s open challenges.

## Adoption

Still niche but growing adoption:

- **Cloud-native startups**
- **Academia** — simple TypeScript without config

## In the Italian context

Limited but growing presence in early-adopter teams.

Update — 2022

From **Deno 1.29 (2022)** the runtime supports **npm: specifier** (`import { z } from "npm:zod"`) bridging the compatibility gap with the npm ecosystem. **Deno Deploy** (2022) is the run-at-the-edge platform executing Deno scripts in global regions with minimal latency — a competitor to Cloudflare Workers and Vercel Edge Functions.

---

_References: Deno 1.0 (13 May 2020). Ryan Dahl (ex Node.js), Deno Company. MIT licence. Rust + V8 runtime. Native TypeScript. URL imports._
