Moving visuals on this page — measured at 0.26% brightness change per frame and zero flashes per second; your reduce motion setting stops them. What moves, and how it was measured

Mathematical plates that draw themselves — prime counts, orbits and lattices rendered live rather than shipped as pictures. It runs continuously while on screen, and it pauses on its own whenever it scrolls out of view.

We measured it rather than guessing: the largest frame-to-frame change in average brightness is 0.26%, and it produces zero flashes per second against the threshold of three set by WCAG 2.3.1. That is well under the limit, and it is not a promise about any individual: if moving images are a problem for you, you should not have to assess ours.

Everything animated on this site honours your system’s reduce motion setting — turn it on in your operating system or browser and these pages stop moving, with nothing else lost. All the mathematics is in the text and the still figures.

Entry 2 of 2 in Machines Run itMeasured

Why we never use floating point Machines

n! computed two ways, live — watch them agree, then quietly stop agreeing

?

Math: n! grows fast enough to leave IEEE-754 double precision's exact-integer range (2532^{53}) at a fixed, known n — not a rare edge case, a certainty. Dev: this site's own internal rule (never floats, only BigInt/exact fractions) exists precisely because of what's about to happen to the float column below.

Both cells compute the same n! as n counts up, live, right now — one in BigInt (unlimited precision), one in an ordinary JavaScript Number, the same IEEE 754 double most languages use for floating-point numbers. They agree exactly through 18!. From 19! on, Number is no longer guaranteed exact — it stays exact through 22! because the factors of two in n! cost no mantissa bits, and at 23! the odd part outgrows 253: from there it is provably wrong for every n after.

exact

float