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.
JavaScript runs code in a single thread around an event loop: while a handler runs, nothing else does, and parallelism has to be moved out into separate workers. Go started from the opposite assumption — its FAQ says outright that the rise of multicore CPUs argued for first-class support for concurrency, and goroutines and channels sit in the language specification itself.
Both have a garbage collector, so the difference is not in memory but in how the work is laid out. And one more: JavaScript is the only language of the four with a written standard, ECMA-262, while Go is described by its own specification with no committee to approve 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