Discussion about this post

User's avatar
Adrien's avatar

The framing of capex as a competitive moat is the right one, but there's a second-order effect that gets overlooked: every dollar Meta commits to gigawatt-scale clusters flows through a finite supply chain — specifically ASML EUV lithography, TSMC advanced nodes, and CoWoS substrate capacity. Meta's $6B Corning fiber deal is a leading indicator of how far downstream these commitments reach. For investors, the more interesting play isn't Meta itself but what this $125B midpoint guidance means for the equipment cycle in 2026–2027: tool orders at AMAT, LRCX, and KLAC tend to lead the buildout by 12–18 months, and that cycle is already in motion. Does the piece's thesis change if the energy constraint (Prometheus Ohio 1GW cluster) turns out to be the binding bottleneck rather than compute capacity?

Jenny Ouyang's avatar

The part about infrastructure becoming the strategy hits differently when you've experienced even tiny versions of this.

I burned through five hosting providers on my first app before I realized the infrastructure problem wasn't something I could optimize around, it was the bottleneck. That experience completely reshaped how I think about deployment costs.

Seeing Meta convert margin into compute capacity at $135B scale is wild, but the underlying logic tracks: when your competitive advantage depends on model performance, infrastructure stops being a cost center and becomes the moat itself.

No posts

Ready for more?