Compiled vs Interpreted Languages — Explained with Examples

Compiled languages are translated entirely to native machine code by a compiler before execution, producing standalone executable files. Interpreted languages are executed line-by-line by an interpreter at runtime, without a separate compilation step. In practice, many modern languages use a hybrid approach.

C, C++, Go, and Rust are traditionally compiled. Python, JavaScript, Ruby, and PHP are traditionally interpreted. However, the boundaries blur: Python compiles to bytecode (.pyc) before interpretation; JavaScript engines (V8 Engine) JIT-compile to native code; Java and C# compile to bytecode (JVM/CLR) which is then JIT-compiled. JIT Compilation and AOT Compilation represent the extremes on this spectrum.

Real-world analogy. An interpreted language is like a live translator at a United Nations speech. The delegate speaks (source code), and the translator interprets into the target language in real-time. A compiled language is like a pre-recorded speech that’s been fully translated and subtitled before the event — ready instantly but harder to change.

Example (Hybrid — Python):

# Python source → compile to bytecode → interpret on PVM
def greet(name):
    return f"Hello, {name}!"
# .pyc bytecode is cached for faster subsequent runs

Example (Pure compiled — C):

// C source → compile → native executable
gcc hello.c -o hello
./hello  // Pure machine code, no runtime compiler

Related terms: JIT Compilation, AOT Compilation, JVM, CLR, Transpiler