I love the material here, but it's mistitled. This isn't about computer science, it's about computers. The introduction doesn't even display much knowledge about the definition of computer science, claiming it's "<i>possibly</i> data structures". It's like calling a book on car repair "automotive engineering from the bottom up."
After skimming the TOC a few times, I guess the more accurate title is "Computer Architecture from the Bottom Up".<p>I don't see any math model like lambda calculus or Turing machine mentioned one it.
Nit note: EPIC is too niche, but so is VLIW. VLIW is taught because the entire approach is about the architectural decision to expose processor state that would normally be controlled by the microprogram in charge of interpreting and timing the macrocode. Effectively, VLIW gives low-level control over to, and depends entire on the intelligence of, the compiler toolchain to correctly manage the processor's internal state. Transmeta Crusoe attempted this, but it was a commercial failure. Soft-updatable microcoded RISC-CISC CPUs and GPUs won.
> Compiled programs have some disadvantages for modern software development. Every time a developer makes a change, the compiler must be invoked to recreate the executable file.<p>Executable files are inessential to compilation.
The first page says:<p>"instead of being stored as bits on a disk the information is displayed as dots on a screen"<p>But the concept of bits has not been introduced.