969: This guy is nuts (TypeScript Doom)

What It Covers

Dimitri Metropolis explains how he built Doom running entirely in TypeScript's type system, taking 11.5 days to compile, and introduces TypeSlayer, a diagnostic tool for identifying TypeScript performance bottlenecks in large codebases.

Key Questions Answered

• •TypeScript Type System Performance: TypeScript types can create matrix multiplications generating hundreds of thousands of union members, causing 100+ second compile times. A five-line fix removed 100 seconds from CI by eliminating accidental type explosions from utility type usage.
• •TypeSlayer Diagnostic Tool: Built in Tauri with Rust backend, TypeSlayer processes multi-gigabyte trace files to expose hidden TypeScript complexity errors that developers silence with TS-ignore comments, revealing performance bottlenecks that slow CI and editor responsiveness without fixing underlying issues.
• •Packaging Native Binaries via NPM: Publish platform-specific binaries as separate NPM packages (like @typeslayer/linux-x64, @typeslayer/darwin-arm64) with a 30-line post-install script detecting user platform. This delivers 9MB executables instead of 200MB+ Node bundles, matching ESBuild's distribution strategy.
• •WebAssembly Runtime in Types: Building Doom required creating a complete WebAssembly runtime purely in TypeScript types, processing 177 terabytes of type data. The project proves practical Turing completeness beyond mathematical theory, demonstrating types can handle physics engines, texture mapping, and sprite systems.