computer sciencehistory of technologycomputer memory
Your Computer Is Forgetting Right Now
The memory that keeps your open tabs alive leaks by design, and the story of how engineers made that harmless is stranger and better than it sounds.
Somewhere inside the machine you are reading this on, a great many tiny electrical states are fading. Not because anything is broken. They were built to fade, and again and again something quietly restores them before the difference becomes too small to read. That is the ordinary working life of DRAM, the memory that keeps your unfinished work in reach, and it is the subject of Chips That Forget.
I came to it the way most people do, through a complaint. A laptop that felt sluggish when too much was open. The processor got the blame, as it usually does. But the pause I was feeling often had little to do with calculation. It was the machine running out of working room and shuffling things off to storage, then fetching them back when I returned. Once I understood that, I wanted to know what the working room actually was. Not the number on the specification sheet, but the object behind the number.
What I found was a lovely piece of engineering honesty. The familiar DRAM cell is little more than a capacitor that holds a charge and a transistor that acts as a gate. It is small, which is the whole point: small enough to repeat in enormous numbers on a single chip. The cost of that smallness is that the capacitor is not a sealed jar. Its charge leaks. So instead of chasing a perfect component, the designers accepted a modest one and built a whole system around caring for it. A controller schedules refresh. Sense amplifiers detect a tiny difference and strengthen it. Reading a cell means restoring it too.
The apparent stillness is produced by repeated action.
That line sits near the heart of the book, and I think it is true of more than memory chips. A great deal of what feels effortless in a computer is really a set of agreed responsibilities, each one unglamorous on its own. I wanted to make those responsibilities visible without asking you to learn circuit notation. You do not need to build a memory controller to read this. I keep the terms that do real work and drop the ones that only make a sentence sound authoritative. When I reach for an analogy, a library, a workbench, a bus on a narrow path, I also tell you where it stops being true, because a metaphor forced to explain every wire does more harm than good.
The book moves outward in steps. First one bit, under the closest look I can give it. Then a row, and how a single row is selected and read. Then a chip, a module in a desktop slot, and the rather different memory placed close to the processor in a phone, where space, heat and energy set the rules. Along the way there is history, and it is told as a series of decisions rather than a parade of heroes: why builders moved from tiny threaded magnetic rings to patterned silicon, what an early memory chip had to prove before anyone would redesign a machine around it, and why so much of the story belongs to factories. An idea can be brilliant. It still has to come off a wafer working, tested and packaged before it can sit inside your laptop.
Then the view widens to the world around the cell. The later chapters follow the companies that make DRAM, the stacked form called high bandwidth memory, and the pressure on factory capacity that has made memory dearer in 2026. I have tried hard not to treat any shortage as a law of nature. When a laptop, a server and a stack of memory beside an accelerator all want the same silicon, the reasons become easier to see, and so does what an advertised speed can and cannot tell you.
Who is this for? Anyone who has looked at a memory figure on a specification and wondered whether it mattered. Anyone who has read a headline about chip supply and felt it was written for someone else. Students of computing who want the physical picture behind the abbreviations, and readers of history who like to see how an engineering choice made in one decade shapes the machines of the next. Above all, I wrote it for the curious person typing a sentence while a call waits in a corner of the screen, which is exactly where the first chapter begins.
If you have ever left a tab open and come back to find it waiting, you have already met the quiet partner in this book without knowing its name. Come and meet it properly. Chips That Forget takes the plain dark rectangle apart, one bit at a time, until the hardware, and the market around it, finally make sense.
More from the journal
More by Bex Calder
- The pause nobody would let me delete 20 Oct 2026
- A reader asks whether it is ever right to throw the whole thing out and start again 15 Oct 2026
- The function everyone was afraid to touch 10 Oct 2026
- What I always notice reopening old code 5 Oct 2026
Discussion
House rules
- Sign how you like, but be one person. You may use the name on your account, a name of your own choosing, or none at all. What you may not do is wear somebody else's: no pen name of ours, no member's name but your own, and nothing that reads as the studio or its staff.
- Argue with the point, not the person. Robust disagreement is welcome; contempt is not.
- Nothing unlawful, hateful or harassing, nothing that identifies a private individual, and no advertising.
- Post only what is yours to post. That includes other people's writing and private correspondence.
- We may hide a remark, remove it, or close an account to the discussions, and we may do so without notice.
What a chosen name is and is not
A chosen name hides you from the room, not from us. Every remark stays linked to the account that wrote it, and the studio can see that link whenever it needs to. Please treat it as a way to speak freely, not as a way to say something you would not put your name to.
Where responsibility sits
Remarks in this thread are written by members and published without prior review. They are the views of the people who wrote them and not those of eQuill Studio. We do not verify their accuracy, and we accept no liability for them or for any decision taken in reliance on them.
If something here breaks these rules or infringes your rights, report it and we will look at it promptly.
House rules
- Sign how you like, but be one person. You may use the name on your account, a name of your own choosing, or none at all. What you may not do is wear somebody else's: no pen name of ours, no member's name but your own, and nothing that reads as the studio or its staff.
- Argue with the point, not the person. Robust disagreement is welcome; contempt is not.
- Nothing unlawful, hateful or harassing, nothing that identifies a private individual, and no advertising.
- Post only what is yours to post. That includes other people's writing and private correspondence.
- We may hide a remark, remove it, or close an account to the discussions, and we may do so without notice.
What a chosen name is and is not
A chosen name hides you from the room, not from us. Every remark stays linked to the account that wrote it, and the studio can see that link whenever it needs to. Please treat it as a way to speak freely, not as a way to say something you would not put your name to.
Where responsibility sits
Remarks in this thread are written by members and published without prior review. They are the views of the people who wrote them and not those of eQuill Studio. We do not verify their accuracy, and we accept no liability for them or for any decision taken in reliance on them.
If something here breaks these rules or infringes your rights, report it and we will look at it promptly.
This thread belongs to this piece alone. Members choose how they are signed, and can change it from the box below. When the studio or the writer joins in, the page says so with a badge, so you always know who is talking.
OPENING THE THREAD…