💻 Code Execution Pipeline
A 3D pipeline showing source code turned into tokens, an abstract syntax tree, machine code or bytecode, and finally instructions executing on CPU cores.
Source code doesn't run directly — it flows through a lexer, a parser, a compiler or interpreter, and finally the CPU. This scene lays that pipeline out in 3D so you can watch tokens, syntax trees and instructions move stage by stage.
🔬 What It Demonstrates
How raw text becomes tokens, how tokens are assembled into an Abstract Syntax Tree, and how that tree becomes either machine code or bytecode before instructions retire on CPU cores.
🎮 How to Use
Adjust execution speed and program size, switch between a compiled and interpreted execution model, choose how many CPU cores are available, and toggle the AST's tree links.
💡 Did You Know?
Many real-world runtimes (Java's JVM, Python's CPython, V8 for JavaScript) blend both models: they compile to bytecode first, then use a Just-In-Time compiler to turn frequently run bytecode into native machine code.
A 3D Three.js pipeline that shows how source code becomes running software: tokens stream from source code through a lexer, get assembled into an Abstract Syntax Tree by a parser, are translated to machine code or bytecode, and finally light up CPU cores as instructions retire.
3D · Three.js / WebGL renderer · 60 FPS target · runs fully client-side, no install