Paul argues that the programming community has spent too much energy deepening type systems—adding dependent types, effect systems, and other sophisticated constructs—while neglecting the need for a more modular building block. He likens the ideal substrate to LEGO parts, simple pieces that can be combined in many configurations without the constraints of traditional functional programming. According to the essay, FP excels at pure calculations but forces developers into synchronous, filter‑only pipelines, which hampers timing, concurrency, and fan‑out required by modern IoT, robotics, and distributed services.

The author proposes five primitives: a minimal transport layer, recursive container and leaf parts, components that go beyond one‑in‑one‑out filters, pure, asynchronous message‑passing with a fire‑and‑forget model, and explicit ports and gates to enforce encapsulation. He cites Unix pipelines as a step toward this vision but notes their single‑dimensional flow limits scalability. By adopting these building blocks, architects could design black‑box abstractions that remain debuggable and replace operating‑system workarounds that currently hide state management.