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.
Rust is the only language of these four whose memory nobody clears: instead of a collector, the compiler tracks who owns what and frees it the moment the ownership ends. Python stands at the opposite edge: reference counting plus cycles, and the programmer does not think about memory at all.
The price is known in advance and is paid at different times. In Python it is paid at run time: the collector works while the program works. In Rust it is paid at writing time: the compiler will not accept code in which the owner is not visible — which is why the mistakes that surface in Python on a live server do not compile in Rust.
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