Author: Brian Kernighan (Unix tools, AWK, The Practice of Programming)

Kernighan is the field’s best writer about programming practice and its most effective critic of languages that are strict without being expressive.

Ethos in his own words

“C is the best balance I’ve ever seen between power and expressiveness.” (Interview with Brian Kernighan, 2000)

“I think that the real problem with C is that it doesn’t give you enough mechanisms for structuring really big programs, for creating “firewalls” within programs so you can keep the various pieces apart.” (Interview, 2000)

“C++ I think is basically too big a language, although there’s a reason for almost everything that’s in it.” (Interview, 2000)

“The languages that succeed are very pragmatic, and are very often fairly dirty because they try to solve real problems.” (Interview, 2000)

“There are only two real problems in computing: computers are too hard to use and too hard to program.” (Linux Journal, 2003)

“Code should be clear and simple-straightforward logic, natural expression, conventional language use, meaningful names, neat formatting, helpful comments-and it should avoid clever tricks and unusual constructions.” (The Practice of Programming)

Defining decisions

Attack a teaching language used in production. “Comparing C and Pascal is rather like comparing a Learjet to a Piper Cub - one is meant for getting something done while the other is meant for learning - so such comparisons tend to be somewhat farfetched.” (Why Pascal is Not My Favorite Programming Language, 1981) On the fixed array bound: “This botch is the biggest single problem with Pascal.” (bwk on Pascal)

Name the missing escape. His conclusion about a strict language without an override is three words: “There is no escape.” (bwk on Pascal) This is the strongest primary-source argument bearing on q16-escape-hatch.

Teach with complete programs. “The examples in this section are each complete, in the sense that they will run as presented; I have tried to avoid code fragments that merely illustrate syntax.” (A Descent into Limbo)

Document removals as design. Limbo, in his description: restricted pointers with “no & (address of) operator”, “no address arithmetic”, “no implicit coercions between types”, “There is no preprocessor”, and an adt that “does not support inheritance, and has no constructors, destructors or overloaded method names.” (A Descent into Limbo)

Label wrong-but-plausible code in the tutorial. “If the input contains any multi-byte Unicode characters, this code is plain wrong.” (A Descent into Limbo)

Where he contradicts Mo

Mo’s laws are unoverridable compiler errors. Kernighan’s Pascal essay is the canonical account of that design failing on programs the rule did not anticipate. His historical claim that successful languages are “fairly dirty” (Interview, 2000) is a direct bet against Mo’s cleanliness.

What Mo could take

ideamaps tostatus
Simplicity, clarity, generality, automation as the judging criteria for every lawd04-style-rules-become-lawsstrengthens Mo
Pascal’s “no escape” as the case for one narrow, auditable overrideq16-escape-hatchcontradicts Mo
Every documentation example is a complete runnable programd01-agents-write-the-codenew idea for Mo
Show the plausible-but-wrong version and label it wrongq09-compiler-diagnosticsnew idea for Mo
Limbo’s removal list as precedent for Mo’s negative spaced06-never-oopalready in Mo

17 Sep 2026: the escape-hatch row was ruled disagree on 13 Sep — it is Robert’s call, recorded on Q16. See research-agenda-2026-09-response.