Position Eeproms Byte Level Granularity Against Bulk Storage

# Position EEPROM's Byte-Level Granularity Against Bulk Storage

## 11. A Product-Positioning Fact, Not a Density Race

EEPROM's byte-level (or small-page) erase and write granularity was a genuine product-positioning characteristic, not an incidental limitation: a system could rewrite a single byte or a handful of bytes of stored configuration data without touching the rest of the array, which fit calibration tables, device serial numbers, user preference settings, and small firmware-adjustable parameters extremely well. That same fine granularity, however, made EEPROM commercially unsuited to bulk, high-density storage, because each cell's erase/write circuitry carried real area and cost overhead that did not scale down the way a simpler bulk-erase architecture eventually would. The practical market split that followed was consistent and durable for roughly a decade: EEPROM occupied the small, frequently-updated configuration-data niche — automotive engine-control calibration constants, instrument calibration tables, appliance control settings — while bulk program and data storage stayed on EPROM, mask ROM, or magnetic/optical media, each chosen for its own reasons.