hn.today

How did Woz write the Apple 1 BASIC before building the computer?

retrocomputing.stackexchange.com319 points176 comments
Screenshot of How did Woz write the Apple 1 BASIC before building the computer?

Commenters describe writing and hand-assembling programs on paper as ordinary practice for early computer hobbyists, especially when assemblers, storage, or even access to a machine were expensive. Several recall writing out addresses, opcodes, and source code, then entering the result by hand and testing it on the target hardware. They say simple instruction sets could be learned by heart, and that the slow, deliberate process encouraged careful planning. Others recall using BASIC to enter machine-code routines or writing code before hardware was ready, then adapting tools once the board existed. One commenter contrasts paper’s discipline and ability to catch logic errors with modern rapid feedback, while another emphasizes how tedious manual assembly could be.

The specific path from Woz’s handwritten BASIC to a working ROM prompts speculation about the intervening tools. One commenter proposes an incremental route: create or adapt a monitor, use an assembler or other computer to generate machine code, and build the interpreter in small steps. Another asks how the ROM itself was programmed, suggesting possibilities such as a separate computer or hardware for toggling address and data pins. These are presented as possibilities, not as a settled account. The comments also reflect admiration for Woz’s skill, alongside personal stories of learning assembly and programming through painstaking work with paper, hex keyboards, cassette tapes, and limited tools.

Read on retrocomputing.stackexchange.com176 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Programming

Aristotle Expands into Rust

Aristotle has expanded its formal verification platform to Rust, allowing developers to prove code meets specifications and contains no undefined behavior, including in unsafe blocks. It can also verify that Rust rewrites behave like their original C code, targeting critical software such as smart contracts and infrastructure. (harmonic.fun)

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.