C

“A general-purpose high-level programming language suitable for low-level programming” — the description on c-language.org, a community information site (design credited to Jorenar) that points at the standard and its resources rather than owning the language. It names portability, interoperability, efficiency and stability as C’s strengths, and lists the revision history: K&R (1978), C89, C90, C95, C99, C11, C17, and C23 (ISO/IEC 9899:2024), published 31 October 2024 with the final draft dated 22 February 2024. The language is maintained by WG14, the ISO standards committee.

T3 — a community site, not the committee’s own publication. It is accurate about the standards lineage and secondary to it; the primary sources are the ISO documents and the WG14 drafts it links.

Its position in the corpus

C is the founding corpus’s only language whose identity is a document rather than an implementation. Every other source here is a project’s home page describing software its authors ship; this one describes a specification that implementations conform to. That is what makes multiple competing compilers normal in C and unusual elsewhere, and it is the strongest case in the spoke for committee governance.

It is also the baseline the rest are arguing against. rust‘s entire safety pitch is aimed at the class of bugs that manual memory management permits. c has no concurrency model in the language at all. What it has instead is the property none of the others claim: interoperability. The C ABI is how the other languages call into anything, including each other, so C’s position is less “an alternative to these” than “the layer they all terminate at”.

Stability as a feature is a claim with a bill attached. Four decades of not breaking programs is why C is everywhere and also why its defaults are the ones the newer languages were designed to escape.

Related

programming-language · rust · memory-management-model · language-governance · synthesis