Apple’s Macintosh puzzle survived cancellation after a weekend rewrite cut it to 600 bytes
Andy Hertzfeld’s account ties a tiny desk accessory to a larger argument over whether serious computers were allowed to be fun.

Apple’s little sliding-tile puzzle had two problems: it occupied too much memory, and some people thought games made the Macintosh look insufficiently serious. Andy Hertzfeld answered the first objection over a weekend. That forced the second one out into the open. A 15-tile game had acquired an office-politics expansion pack.
In his first-person account, Hertzfeld explains that the original Mac could run one main application while small desk accessories shared its memory. Calculators and clocks belonged there, but he also wanted games to show that the machine could be fun. Puzzle let a user slide numbered tiles around a four-by-four grid and practice using the mouse along the way.
Hertzfeld originally wrote it in Pascal as a demonstration that desk accessories could use that language. The program had to link a runtime containing code the game didn’t need. Its size exceeded 6 KB, with much of that occupied by the runtime. A small game had brought an unexpectedly large overnight bag.
By fall 1983, the team had to decide what would ship. Some analysts had described the graphical interface as game-like, which made marketing uneasy about including an actual game. Software manager Jerome Coonen told Hertzfeld that Puzzle would be removed, with memory and disk space among the reasons.
Hertzfeld offered a smaller version and asked whether size really was the objection. Coonen set a target around 600 bytes and a weekend deadline because the manuals were about to go to print. Hertzfeld recalls getting the rewrite done in a few hours on Saturday, removing the need for the bulky Pascal runtime by using assembly language.
The result shipped in the first release. It remained for years, although the account says it was subsequently rewritten more than once. The useful comparison is the same accessory before and after its implementation changed, rather than a sweeping claim that every Pascal program wastes memory or every assembly rewrite saves ninety percent.
The episode makes an old constraint unusually visible. Memory pressure was real, yet it was also tangled up with a judgment about what customers should be allowed to enjoy. Once the game met the size condition, the team had to live with its own answer. A measurable condition gave the small, supposedly frivolous feature a way to stay.
Hertzfeld describes the decision as resisting an “all business view of the customer.” That is his recollection of the dispute, and the source for this story, rather than a claim that everyone at Apple shared a single view of games. The account names the people and the compromise that settled this particular accessory.
Tiny built-in amusements can also make an unfamiliar interface approachable, provided they justify their memory use within the machine’s limits. Puzzle had a concrete limit and somebody willing to meet it before Monday.
Saturday saved a little playtime.