Reading Programing Language Specs
Mathematica, has no spec. It has 1k pages manual. I read cover to cover, word for word, 3 times in continuous setting, in separate years, from 1993 to 1999.
Scheme lisp r4rs, is also the shortest and lean. I read at least 3/4 of it in 1999. But back then, i don't have much lang spec experience. don't understand it that much.
perl, has no spec. It has docs, i read cover to cover several times from 1998 to 2004.
PHP has no lang spec. (at least during 2010s). I read basically the entire doc in 2006, doing a project. It is, the most easy-reading, understandable.
SVG spec i read most starting 2015, parts multiple times. As with most w3c dom stuff, it's written in a incomprenhensible semi adacemic semi industrial way. Bloated with jargons and words that pretends to be comprehensive and precise but actually is neither.
Racket scheme lisp. I read parts of the spec around 2015. Doing some homework in racket for someone. lol.
emacs lisp, has no lang spec per se. It's 1k pages manual, i read some 70% over the decade since 2006.
Python has a semi spec. They call the “language reference” section in the doc. Full of imprecision, conceit, irrelevance. Python folks always trying to sell you something, with passive aggression.
Clojure, has no spec. I spend close to 1 year full time, spread between 2014 to 2016 reading its doc. (it doesn't really have doc neither. It has doc string, and collection of “essays/concepts”) Extremely dense. It has lots problems, mostly due to intentional mix with Java.
Golang spec is the most concise and precise, and shortest. (comparable and surpass Scheme's spec in concision, precision, and brevity.) I read parts in 2018, and understand it well.
See also: Emacs Idolization: Have You Read the Emacs Manual From Cover to Cover?
more articles on doc, see doc by dummies
If you have a question, put $5 at patreon and message me.