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.
These two differ on everything in the table: dynamic against static, garbage collection against ownership, an engine compiling on the fly against native code produced ahead of time, exceptions against a Result in the function's type. The twenty years between them — 1995 and 2015 — are also twenty years of different problems: one was written to bring a page to life, the other so that there would be nothing to crash.
They share one thing, and it is not obvious: both treat safety as the language's duty rather than the programmer's. JavaScript does it by not letting you touch memory at all; Rust by not letting code compile when the owner is not visible. These are two answers to the same question, which is why WebAssembly, the target Rust compiles to, lives beside JavaScript rather than instead of it.
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