Nvidia's CEO just admitted to having an affair with a suspected Chinese spy. He said so in a memo to employees, sent on a Sunday, and he apologized to his wife for being unfaithful.
Why should a developer care? Because this is now a national security story, and Nvidia sits under nearly every serious AI training run. The board has opened an independent investigation into the security concerns, and the CEO says he will cooperate fully. If your team depends on Nvidia supply, export rules and chip access could tighten fast.
The numbers matter here. Nvidia plans to sell 27,500 next-generation Rubin chips to Japan so Japan can build a homegrown foundational AI model for robots. That deal is now under a much brighter spotlight.
Watch the investigation's findings and whether the Japan chip deal stays on schedule. Those outcomes will decide whether this stays a personal scandal or becomes a supply chain problem.
OpenAI just closed $11 billion at a $1.25 trillion valuation, and the round is smaller and cheaper than what it wanted. The original ask was $30 billion or more at $1.4 trillion, and some investors pushed for $1.5 trillion. Then AI stocks sold off, and the deal shrank.
Why should you care? Because this round is a test of whether AI demand still beats supply. OpenAI's business grew 70% quarter over quarter in Q3, its enterprise business doubled, and revenue splits roughly evenly between consumer and enterprise. If you're building on OpenAI's APIs, that enterprise growth is the signal that pricing and capacity won't stay friendly forever.
The numbers: SoftBank and Abu Dhabi's MGX took part. OpenAI has 1.2 billion weekly ChatGPT users and a $1 billion ads run rate by August. The rest of the round could bring the total to $20 billion, and a separate report puts another $9 billion on the table. That second portion hasn't closed yet.
What to watch: whether the follow-on money actually lands. A full close at the higher end would signal investors still believe the demand story. A stall would say the market is repricing AI. Let's dive deeper…
In today's ContentBuffer update: