Why Use Binary?
Computerphile
Argues that binary won because two states are the easiest to tell apart reliably in a noisy physical circuit, not because two is mathematically special.
link checked 17 Sept 2026The machine underneath the abstraction.
13 topics · 17 curated works
No prior grounding assumed.
Why Use Binary?
Computerphile · 2015
Argues that binary won because two states are the easiest to tell apart reliably in a noisy physical circuit, not because two is mathematically…
Assumes you know the vocabulary.
Validity of the Single Processor Approach to Achieving Large Scale Computing Capabilities
Gene M. Amdahl · 1967
Shows that the serial fraction of a program bounds the speed-up available from parallel hardware, no matter how many processors are added.
+7 more at this level
Primary sources and full treatments.
The Synthesis of Two-Terminal Switching Circuits
Claude E. Shannon · 1949
Gives a general procedure for building a switching circuit that realises any prescribed Boolean function using the fewest contacts, turning circuit…
+7 more at this level
12 of 17 works
Computerphile
Argues that binary won because two states are the easiest to tell apart reliably in a noisy physical circuit, not because two is mathematically special.
link checked 17 Sept 2026Gene M. Amdahl
Shows that the serial fraction of a program bounds the speed-up available from parallel hardware, no matter how many processors are added.
3 pageslink checked 17 Sept 2026Alan Jay Smith
Surveys cache design choices — size, associativity, line size, write policy — and argues locality of reference, not raw memory speed, is what a cache actually exploits.
John L. Gustafson
Argues Amdahl's Law wrongly assumes problem size is fixed, and that programmers instead scale the problem to fill available processors, so speed-up grows with machine size rather than saturating.
Wm. A. Wulf & Sally A. McKee
Projects that if processor speed keeps outpacing DRAM latency at their historical rates, most programs will eventually be bound entirely by memory access rather than computation.
Owens et al.
Argues that a GPU's fixed-function pipeline had, by the mid-2000s, become general-purpose enough to reprogram for non-graphics problems, and catalogues what kinds of problems map onto it well.
Mark D. Hill & Michael R. Marty
Extends Amdahl's Law to chips built from many identical or specialised cores, showing that a small number of powerful cores can beat many weak ones on partly-serial workloads.
Samuel Williams, Andrew Waterman & David Patterson
Plots achievable performance against a kernel's arithmetic intensity, showing from a single chart whether a program is limited by compute throughput or memory bandwidth.
link checked 17 Sept 2026Onur Mutlu (ETH Zurich)
Works through why splitting instruction execution into overlapping stages raises throughput, and what data, control and structural hazards it introduces in exchange.
Claude E. Shannon
Gives a general procedure for building a switching circuit that realises any prescribed Boolean function using the fewest contacts, turning circuit minimisation into a solvable algebraic problem.
Gene M. Amdahl, Gerrit A. Blaauw & Frederick P. Brooks Jr.
Defines architecture as the programmer-visible interface kept separate from implementation, and specifies one instruction set meant to span an entire family of machines at different price points.
Robert M. Tomasulo
Describes a hardware scheme that lets independent instructions execute out of program order by renaming their destination registers, resolving hazards without a compiler's help.