3 ms·
Different books have different goals. K&R is short, but the standard is ~700 pages. The Rust book is over 400 pages, but contains entire chapters of just "let's
by steveklabnik 9y ago
Different books have different goals. K&R is short, but the standard is ~700 pages. The Rust book is over 400 pages, but contains entire chapters of just "let's build a project together." There's no spec yet like C has. Writing styles differ dramatically, K&R are more concise than I am, and don't dive into some details as much.
Then, you may also consider the framing of "simple" vs "easy", they're not the same thing. And that's even if we agree that C is simple in the first place, which I personally consider not true.
Basically, I don't think that comparing page counts of random documents says anything meaningful about language complexity.
- crispinb 9y agoAs an aside I don't have time or any purpose beyond curiosity to learn Rust right now. But having glanced through the Rust book a few times, I wish I did. It's the sort of book (a bit like K&R in this sense) that could lead one astray ..
- steveklabnik 9y agoThank you; even saying "a bit like K&R" at all is high praise to me. That said, not everyone likes my writing style, so I'm glad that there are other books coming out as well.
- geezerjay 9y ago> Different books have different goals. K&R is short, but the standard is ~700 pages. ISO/IEC 9899:1999 is 554 pages, and the annex alone takes around 140 pages. ANSI ISO 9899:1990 is even shorter: 230 pages.
- steveklabnik 9y agoI'm going by ISO/IEC 9899:201x, the draft, since I have not paid for the spec. This does include annexes, but some of them are normative... Really though, this just furthers my point; page count is a terrible metric for this.