From 5fe2f95c8adfc64eaf4fd1e0cee4717152a2d8fd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ahmet=20O=CC=88mer?= Date: Wed, 14 Oct 2026 20:45:32 +0200 Subject: [PATCH] docs: update the handbook intro to 30 years of JavaScript --- packages/documentation/copy/en/handbook-v2/The Handbook.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/documentation/copy/en/handbook-v2/The Handbook.md b/packages/documentation/copy/en/handbook-v2/The Handbook.md index d3712dcc2332..46718910d895 100644 --- a/packages/documentation/copy/en/handbook-v2/The Handbook.md +++ b/packages/documentation/copy/en/handbook-v2/The Handbook.md @@ -8,7 +8,7 @@ handbook: "true" ## About this Handbook -Over 20 years after its introduction to the programming community, JavaScript is now one of the most widespread cross-platform languages ever created. Starting as a small scripting language for adding trivial interactivity to webpages, JavaScript has grown to be a language of choice for both frontend and backend applications of every size. While the size, scope, and complexity of programs written in JavaScript has grown exponentially, the ability of the JavaScript language to express the relationships between different units of code has not. Combined with JavaScript's rather peculiar runtime semantics, this mismatch between language and program complexity has made JavaScript development a difficult task to manage at scale. +Over 30 years after its introduction to the programming community, JavaScript is now one of the most widespread cross-platform languages ever created. Starting as a small scripting language for adding trivial interactivity to webpages, JavaScript has grown to be a language of choice for both frontend and backend applications of every size. While the size, scope, and complexity of programs written in JavaScript has grown exponentially, the ability of the JavaScript language to express the relationships between different units of code has not. Combined with JavaScript's rather peculiar runtime semantics, this mismatch between language and program complexity has made JavaScript development a difficult task to manage at scale. The most common kinds of errors that programmers write can be described as type errors: a certain kind of value was used where a different kind of value was expected. This could be due to simple typos, a failure to understand the API surface of a library, incorrect assumptions about runtime behavior, or other errors. The goal of TypeScript is to be a static typechecker for JavaScript programs - in other words, a tool that runs before your code runs (static) and ensures that the types of the program are correct (typechecked).