Scope. This offline atlas records common, maintained implementations and official first-class
targets. A language can appear in more than one category where that reflects a supported implementation or
target. “Kind” is the family a language belongs to — general-purpose language, assembly, shell, query language,
or portable bytecode.
Typing. Typing is split into two filter sections: “Typing” (static, dynamic, or gradual) and
“Typing strength” (strong or weak). “Gradual” denotes a language that deliberately combines static and dynamic
checking. “Strong” and “weak” follow common coercion and implicit-conversion conventions, which are inherently
less formal than static/dynamic typing.
Execution. “Compiled” includes ahead-of-time, bytecode, and transpilation workflows.
“Interpreted” includes a standard interpreter or VM execution path. Both may apply, especially to VM and JIT
languages.
Platforms. A platform tag means the language has an established implementation, SDK, or
first-class compilation target there. It does not mean every program runs there without platform-specific
tooling.
Runtimes. Runtime tags describe the primary execution ecosystem surfaced by the official
implementation. “Standalone executable” and “WebAssembly runtime” are distinct from a language-specific
interpreter or a VM family.
Sources. Each entry links to an authoritative project or standards homepage. Review dates and
source notes are shown on the language detail page. When a capability depends on a specific implementation or
version, the note says so instead of presenting it as universal.