The autoregressive bottleneck
Every mainstream LLM generates text the same way: predict token 1, append it, predict token 2 given token 1, and so on. This autoregressive loop has deep strengths (an exact factorization of the sequence probability, and a perfect fit for the KV-cache serving stack), but one structural cost: generation is sequential by construction. A 1,000-token answer requires 1,000 dependent forward passes; no amount of parallel hardware removes the dependency chain, because token cannot be computed before token exists.
The previous lessons built machinery with the opposite character: diffusion and flow models generate the whole object at once, refining every pixel in parallel over a handful of passes. Applying that to text is the obvious temptation, and it promises more than speed: a model that drafts globally can naturally infill a gap given both sides, revise what it already wrote, and enforce document-level structure, all awkward for a model that can only append.
Two obstacles stand in the way, and they define this lesson: text is discrete (you cannot add Gaussian noise to token 17,432), and the autoregressive incumbent is extraordinarily strong.

