Understanding How JavaScript Works: From Interpreted vs. Compiled Languages to the V8 Engine Execution Process

Interpreted and Compiled Languages

JavaScript is traditionally classified as an interpreted language, meaning its source code is executed line‑by‑line by an interpreter, whereas compiled languages such as C, C++, Rust, and Go are transformed into machine code through a build step before execution.

JavaScript Engine

A JavaScript engine parses, interprets, and optionally compiles JavaScript code. Modern browsers embed engines like Google’s V8 , Firefox’s SpiderMonkey , Microsoft’s Chakra , and Apple’s JavaScriptCore . The engine reads a script, converts it to an abstract syntax tree (AST), generates bytecode, and may JIT‑compile hot code paths into optimized machine code.

ECMAScript and Engine Relationship

ECMAScript defines the language standard (e.g., ES6). JavaScript engines implement this specification and may add extra features such as garbage collection. New proposals progress through TC39 stages before being adopted by engines.

Runtime Environment

JavaScript cannot run in isolation; it needs a runtime like browsers or Node.js . The runtime provides APIs for events, networking, timers, and the event loop, coordinating with the engine’s single‑threaded execution model.

Why JavaScript Is Single‑Threaded

The language’s design focuses on DOM manipulation and user interaction, avoiding complex synchronization issues that arise with multiple threads. Web Workers offer a way to run CPU‑intensive tasks off the main thread while keeping the core engine single‑threaded.

Call Stack Execution

The call stack records function calls as stack frames. Each new function pushes a frame onto the stack; returning from a function pops the frame. Heavy stack frames can cause UI jank because the single thread is blocked.

Parsing and Execution in V8

V8’s workflow consists of three main components:

Parser – converts source code into an AST.

Ignition (interpreter) – turns the AST into bytecode and gathers profiling data.

TurboFan (compiler) – uses the profiling data to compile hot bytecode into optimized machine code (JIT).

Lexical and Syntax Analysis

Lexical analysis tokenises the source into tokens such as keywords, identifiers, literals, and operators. Syntax analysis then builds the AST from these tokens.

const 公众号 = 'code秘密花园';

Bytecode vs. Machine Code

Bytecode is an intermediate representation executed by the interpreter; machine code is native CPU instructions generated by the JIT compiler for hot paths, improving performance.

Conclusion

The article provides a high‑level overview of JavaScript’s execution pipeline, from source code to the engine’s internal stages, and points readers to deeper resources such as V8 source code and related technical articles.