“There is no avoiding the carnage to come, outside of there being somewhere in the order of ten to a hundred times the demand for AI compute by 2030 that exists today, which would require AI compute to be larger than the $779 billion that the software industry earns annually.”
Our reading, the sentence that was checked:
The carnage to come cannot be avoided unless there is somewhere in the order of ten to a hundred times today's AI compute demand by 2030, which would require AI compute to be larger than the $779 billion the software industry earns annually.
Assessment: Unresolved Not yet due on 2026-10-29 Evidence as of
Where and when Ed Zitron wrote it
Where's Your Ed At, Let AI Burn, paragraph 88.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment wyea-let-ai-burn-4cb150-a2
We recorded 34 claims from this post. See every claim from this post.
The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2026-07-07. This page does not claim the wording was captured then.
What the claim commits to
- Kind
- Conditional forecast
- Deadline, as the speaker wrote it
- “by 2030”
- Deadline state when assessed
- Not yet due
- Deadline state on 2026-10-29
- Not yet due (the release’s reference date)
Conditions
- unless AI compute demand is somewhere in the order of 10 to 100 times today's by 2030 (antecedent, stated by the speaker)
From the speaker
- no avoiding the carnage to come
- outside of
- ten to a hundred times the demand for AI compute
- by 2030
- that exists today
- larger than the $779 billion that the software industry earns annually
Our interpretation
- The exception states a necessary condition for avoiding collapse. It does not promise that sufficient demand growth would prevent collapse.
- Today refers to July 7, 2026. By 2030 allows through December 31, 2030.
- The ordinary reading of carnage is widespread severe business failures and investment losses across the AI sector.
- Demand below ten times the baseline is the clearest case in which the exception has not occurred. The wording does not identify a single threshold within the ten-to-one-hundred-times range.
- The 2030 deadline explicitly governs demand growth; the timing of the resulting collapse is less clear.
- The dollar comparison requires annual compute spending or revenue, but physical compute demand cannot be converted into dollars without prices and a defined market boundary.
Counts as supported if: Comparable measurements establish that demand failed to reach the required scale by the end of 2030, and the relevant AI investment cycle produces widespread severe failures and losses. The dollar implication additionally requires a documented conversion between demand and annual compute spending.
Counts as contradicted if: A completed relevant investment cycle avoids severe AI-sector collapse despite demand remaining below the necessary scale-up. The monetary implication could separately be contradicted by comparable demand and price measurements showing the claimed growth without exceeding the stated annual dollar benchmark.
Prospective: these criteria were frozen before the deadline, while the outcome was not yet public.
Current assessment
Did the forecast come true?
Outcome: Unresolved
The record was checked, and the evidence available by the cutoff does not settle it.
Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.
- Evidence as of
- Deadline state when assessed
- Not yet due
- Assessment recorded
- Policy version
- 2026-10-28.7
Rationale
J.P. Morgan's October 19, 2026 report projected AI capital expenditures approaching $1 trillion in 2026 [e1]. This is a spending forecast, not a measurement of realized compute demand through 2030 [e1]. It cannot settle the end-2030 demand condition, the predicted sector failures and losses, or the claimed conversion from demand growth to annual dollars [e1].
Limitations
- The supplied projection provides no comparable July 2026 demand baseline and realized 2030 demand series [e1].
- It does not verify the $779 billion software-revenue benchmark or a conversion from physical compute demand to annual spending or revenue [e1].
- The contract leaves the demand unit, exact growth threshold and timing of sector-wide failures insufficiently specified.
Evidence (1 item)
Context only: J.P. Morgan,
AI capital expenditures are projected to approach $1 trillion in 2026.
Why it matters here: This is a projection of capital expenditures. It does not establish purchased compute demand, annual software revenue or a realized 2030 outcome.
- Publisher
- J.P. Morgan
- Kind of source
- Secondary summary
- Measures
- Global AI industry aggregate, Projected AI capital expenditures, USD trillions, estimate, 2026-01-01 to 2026-12-31
- Describes events of
- Public from
What would settle it
Comparable demand measurements from July 2026 through December 31, 2030, together with financial and insolvency records establishing the relevant investment cycle's failures and losses or their absence. The monetary component also requires comparable prices, a defined compute market and a verified source and period for the software-revenue benchmark.
Where it was said (1)
Said once in the sources this register covers.
: Where's Your Ed At, Let AI Burn
There is no avoiding the carnage to come, outside of there being somewhere in the order of ten to a hundred times the demand for AI compute by 2030 that exists today, which would require AI compute to be larger than the $779 billion that the software industry earns annually.
- Where
- paragraph 88
- Published
- 2026-07-07
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment wyea-let-ai-burn-4cb150-a2: Current. Outcome: Unresolved. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.