Exercise 3: Minimalism as a Limitation vs. as an Earned Constraint — Possible Solution ==================================================================== "MINIMALISM AS A LIMITATION" — WHAT THAT WOULD MEAN ------------------------------ Under this reading, the 6502 would be minimal because the design team simply couldn't build (or didn't think to build) something more capable — a chip that does less because it fell short of what a "real" or "complete" processor should be. This framing treats every missing feature as a gap or a failure relative to some more capable baseline. "MINIMALISM AS AN EARNED DESIGN CONSTRAINT" — WHAT THIS CHAPTER ACTUALLY ARGUES ------------------------------ This chapter argues the opposite: the 6502's minimalism was the DELIBERATE, direct consequence of a specific, chosen goal (the $25 price target from cpu8bit1-1), not a shortfall. Per this chapter's own "What Minimalism Doesn't Mean" section, nothing a real program genuinely needs was left out — arithmetic, memory access, branching, subroutines, and a stack are all present. What was left out was redundancy that the tight transistor budget genuinely couldn't afford, and every included feature had to justify its own transistor cost against that budget. That's "earned" in the sense that the chip's actual shape is a direct, traceable outcome of a real constraint being satisfied well, not evidence of the design falling short of some ideal. CONNECTING BACK TO CPU8BIT1-1'S "FOUNDING FACT" EXERCISE ------------------------------ cpu8bit1-1's own exercise established that the $25 price point wasn't just an interesting detail -- it was the actual design brief the 6502 team was working toward from the start, which this chapter then traced concretely through the die-size/yield relationship into an explicit ~3,500-transistor budget. Read together, the two chapters make the same point from different angles: the 6502 isn't "a chip that couldn't do more" — it's a chip whose every feature was DELIBERATELY chosen to fit inside a real, non-negotiable manufacturing budget, which is precisely what "earned design constraint" means as opposed to "limitation." WHY THIS WORKS AS AN ANSWER ------------------------------ It defines both framings clearly and contrasts them directly, ties the "earned constraint" reading specifically to this chapter's own "What Minimalism Doesn't Mean" section (redundancy cut, core capability kept), and explicitly connects the reasoning back to cpu8bit1-1's own founding-fact exercise rather than treating the two chapters as unrelated.