seven questions, the same to both, and the document each answer is written in
Built as a memo rather than a table: the thing worth hanging it up for reads across the room, with the full reference in smaller type below it.
Three sizes in one archive — from a sheet on the fridge to a poster on the wall.
Every answer comes from the language's own page or its standard. Checked 4 August 2026.
Go and Rust appeared almost together — 2009 and 2015 — and both were solving the same problem: how to write systems code without paying for it in memory bugs. Their answers part on a single row of the table. Go took a garbage collector and, as its FAQ puts it, «garbage collection alone»; Rust took none, handing the work to the compiler and the ownership system.
Everything else grows out of that one decision. In Go an error is an ordinary value beside the result; in Rust it is in the function's own type and the compiler will not let it be forgotten. Go promises to build a large executable in seconds; Rust promises not to accept code in which two threads may touch the same thing. Both compile ahead of time, and both leave one native binary behind.
Why the numbers can be trusted. Every countable number here is computed from data rather than typed in, and the sheet must pass 6 independent checks before it is allowed to build — how many items there are, the order they come in, and the claim in the highlighted box itself. If one fails, there is no file.
ten tasks, the year of each, the system, the figure — and the human it was measured against
who published each standard, when, what it does to the sound, and how many bits per second it allows
two scales · 1000 and 1024 · why a drive looks smaller
main axis and cross axis · which property belongs to which