Programming Languages Hub

The language catalog: one page per language, each covering its origin, the design ideas it introduced, and its honest 2026 status. For the historical through-line — six technical regimes from manual memory to AI-native coding — see Programming Language Evolution; for the theory that distinguishes them, Type Systems Comparison and Functional Programming Foundations.

Systems languages

C — the pointer-memory lingua franca beneath every OS
C++ — multi-paradigm performance: AI engines, HPC, games
Rust — ownership and borrowing: memory safety at zero cost
Zig — comptime and explicit memory; the C-replacement bid
Assembly — the ISA surface: x86, ARM, RISC-V
Ada — high-integrity and formally verifiable via SPARK

Managed / JVM and .NET

Java — enterprise standard-bearer; ZGC-era JVM performance
C# — .NET, Unity, and Native AOT
Scala — OO-functional fusion on the JVM; Spark's language
Go — CSP concurrency; the cloud-native default
Swift — Apple's safe systems language, Swift 6 concurrency
Objective-C — the message-passing predecessor, in legacy service

Web and scripting

JavaScript — the engine of the web
TypeScript — static types over JS; the professional default
Python — AI/data lingua franca; the GIL-removal era
Ruby — developer happiness; YJIT + Rails 8
PHP — 77% of the web; FrankenPHP-era performance
Perl — the text-processing era's duct tape
SQL — the relational constant since 1974

Functional, logic, and research lineages

Lisp — homoiconicity and GC, since 1958 (see also LISP in foundations)
Prolog — logic programming; neuro-symbolic revival
Smalltalk — pure OOP and the live IDE
Bend — interaction-net parallelism on GPUs
Mojo — Python syntax at CUDA speed for AI infrastructure

Historical foundations

Fortran — first high-level language; still the HPC yardstick
COBOL — the business-logic bedrock under global banking
Algol — block structure and BNF; ancestor of the C family
Pascal — structured programming's teaching language

Choosing among them

Paradigm and ecosystem beat syntax: memory-safety requirements point to Rust/managed runtimes; AI/data work follows the Python ecosystem; cloud infrastructure defaults to Go; enterprise longevity favors Java/C#; and interop constraints (JVM, .NET, C ABI) usually decide more than language merit. The theory behind these trade-offs: Type Systems Comparison, Compiler Design Basics, and Concurrency and Synchronization.