Sam Altman Is Half Right About Your RAM
Altman called local inference a terrible use of scarce RAM. On compute he has a point. On memory, a bankruptcy and a wave of bans this month say otherwise.
On October 29, a clip from the Cheeky Pint podcast became the most upvoted r/LocalLLaMA thread of the month: Sam Altman calling local inference "a terrible allocation of scarce resources." It sits at 6,463 upvotes and 2,826 comments, and the top reply, at more than 3,700 upvotes, is three words: "I smell fear."
The mockery is easy. I think the more useful reading is that he is half right, and the half he skips is the part that matters for anyone building with AI.
The half he gets right
Here is the core of the argument, as transcribed by The Verge:
"It's quite terrible to have everybody have a bunch of the world's limited supply of DRAM sitting in their own computer and being used five percent of the time."
On pure utilization, that is hard to argue with, and the thread's second most upvoted comment conceded as much: "He's not wrong about it being inefficient though, but that's not his business how we use our inference that we paid for with our own money."
It also helps to know who is talking. The Verge framed the interview bluntly: "As OpenAI's buying spree squeezes the world's supply of RAM, its CEO explains why he needs so much." According to the same piece, memory makers have long-term deals with cloud operators and projects like OpenAI's Stargate that reserve much of the world's RAM output for the next few years. Still, for raw compute, renting is often the rational call. A GPU that idles most of the day is a bad investment for plenty of people.
The half he skips
Compute is a commodity. Memory is not. Two other stories from the same month show the difference.
On October 12, Character.AI filed for Chapter 11 to run a court-supervised sale of the company, with Disney lined up as lead bidder for some assets. Its own announcement is candid: "If such a bid is unavailable, however, the platform will be wound down." To their credit, users can export their data. But the platform that holds years of companion conversations is now being sold, "all or substantially all" of its assets, and there is precedent for what that can mean for user data: in June 2025 a bankruptcy court approved the $305 million sale of 23andMe, genetic data of millions of customers included, to a nonprofit led by its founder.
Then there are bans, the month's other recurring thread. "Another reason to own your own compute. Your account may get banned in a sneaky update" collected 1,683 upvotes. When an account goes, access to everything stored inside it usually goes with it: chat history, saved memories, project context. One commenter drew the line I keep coming back to: "It's always worth distinguishing between commodity APIs and APIs from companies that think they've got you locked in."
Rent the compute, own the memory
The split I would make is simple. Models are interchangeable, and in practice they get swapped every few weeks anyway. What compounds is memory: the accumulated context about your work, your preferences, your decisions. That should live in a store that is decoupled from whoever runs the model, in an open format you can export, ideally on hardware you control.
That is the rule I build Uteke around. It is an agent memory engine that runs as a single offline binary with no API keys, or as a hosted version at uteke.app if you would rather not run anything. Yes, the second option is a cloud. I hold it to the same standard I am arguing for here: full export whenever you want, and the identical open-source engine runs on your own machine, so leaving costs a download instead of a rewrite.
A useful test for any AI product you depend on: if the company disappeared tomorrow, what would you still have? For the model, "a different model" is a fine answer. For the memory, the answer should be "all of it."
The CodeCora blog has a related piece on which saved AI knowledge rots and which survives: Your AI Notes Are Rotting.
Comments ()