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.
On the first four questions these two answer almost alike: types are checked while the program runs, memory is cleared by a garbage collector, errors are caught with try. The difference that is not obvious sits in the «standard» row: JavaScript is described by ECMA-262, re-issued every year, while Python has no standard at all — it is defined by its own documentation and the PEP process, with CPython as the reference.
The consequence is practical. A language with a standard has to be understood the same way by every engine, which is why old code in a browser still runs ten years later. A language without one is defined by its implementation: in Python the question «is this the correct behaviour» is settled by CPython, not by a committee.
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