Interactive Bit-Grid Base Converter

George Stibitz, a Bell Labs mathematician, built the first working binary digital computer in November 1937 on his kitchen table using two telephone relays, a flashlight bulb, and scraps from a tobacco tin. He called it the "Model K" for Kitchen. The machine added one-bit binary numbers and displayed the result with the bulb. Stibitz's insight - that any arithmetic could be performed by chaining two-state on/off devices - became the foundational principle of every digital computer ever built. Within three years Bell Labs had scaled the design into the Complex Number Calculator, demonstrated remotely over telegraph in 1940 (one of the earliest examples of distributed computing).

The mathematical underpinnings predate Stibitz by 80 years. George Boole's 1854 book "An Investigation of the Laws of Thought" introduced what we now call Boolean algebra: a calculus of logical propositions with only two truth values, True and False. Boole was working on philosophical logic, not engineering, and his book was largely ignored until Claude Shannon's 1937 MIT master's thesis proved that Boolean algebra could describe electrical switching circuits. Shannon showed any combinatorial logic could be implemented with relay networks - the theoretical bridge from Boole's symbols to physical hardware.

Hexadecimal became the standard human-readable representation of binary data during the IBM System/360 era starting in 1963. The System/360 used 8-bit bytes (a term coined by Werner Buchholz at IBM in 1956) and the engineers needed a way to print memory dumps that humans could read without counting individual bits. Hexadecimal - two digits per byte - was the obvious choice. IBM's System/360 Principles of Operation manual standardized the digits 0-9, A-F for values 10-15, and this convention spread to every subsequent computer architecture. Earlier machines used octal (DEC PDP-8 had 12-bit words that split into four octal digits), but 8-bit bytes made hex the better fit.

Octal made its biggest mark on Unix file permissions. When Ken Thompson and Dennis Ritchie designed the original Unix filesystem at Bell Labs in 1971, they needed to encode three permission types (read, write, execute) for three principals (owner, group, world). That is exactly 9 bits, which fits in three octal digits. The chmod command was born: chmod 755 became universal shorthand. The decision was so natural and elegant that 55 years later every Linux, macOS, and BSD system still uses the same encoding, and developers still mentally translate 755 to rwxr-xr-x without thinking about it.

Hex URL encoding entered the World Wide Web through RFC 1738 (December 1994), which standardized how special characters in URLs are percent-escaped. The percent sign followed by two hex digits represents a byte that cannot appear literally in a URL. So %20 is a space (0x20 = 32 = ASCII space) and %3F is a question mark. The same encoding pattern was later adopted by the IRI standard for international URLs and the data: URL scheme. Every "email me a link with my form data in the query string" chain you have seen since 1995 uses hex percent-encoding under the hood.

The arrival of base-64 was driven by email. RFC 2045 (1996) defined MIME, the standard for sending binary attachments through SMTP - a protocol that historically only handled 7-bit ASCII text. Base-64 encodes 3 binary bytes into 4 printable ASCII characters, a 33% size penalty in exchange for compatibility with every mail server on the planet. The same encoding showed up in JWT tokens (RFC 7519, 2015), data URLs in HTML, and even Basic HTTP authentication. Whenever you need to ship binary bytes through a text-only channel, base-64 is the de facto answer.

JavaScript's BigInt landed in 2020 with the ES2020 specification. For 25 years before that, all JavaScript numbers were IEEE 754 double-precision floats, which silently lose precision for integers above 2^53. This caused real bugs: cryptography libraries shipped their own bigint implementations as JS objects, Twitter IDs got corrupted when treated as Numbers, and any 64-bit integer protocol required workarounds. BigInt (denoted by the n suffix, like 12345n) is now native to all modern browsers and Node.js. This converter uses BigInt throughout, which is why the 100-digit demo (2^333) computes instantly without any rounding error.