Modal Made Crystal Clear · chapter 1: The End of Paying for Idle
Two feedback loops
2026-09-05
The traditional cycle has five stops between an edit and evidence; Modal's has one command. The build still happens, but in the cloud, cached, and off your critical path.
Below: the paragraph from the book that builds this idea, then the diagram itself (Figure 1.3), and a recap. About a minute of reading.
That goal is why the Rust runtime and the virtual file system exist. Fast container boots are not a vanity benchmark; they are what makes it tolerable to run your code in the cloud every single time you save a file. Bernhardsson's summary of the payoff: "Building a 100GB container, and then booting up 100 of those containers, you can do the whole thing in a few seconds." Figure 1.3 puts the two loops side by side.
Recap
- The idea: The traditional cycle has five stops between an edit and evidence; Modal's has one command.
- The picture: Figure 1.3, from chapter 1 ("The End of Paying for Idle") of Modal Made Crystal Clear.
- Go deeper: the chapter builds this step by step, with recipes and sources at the end.
This diagram is one of many in Modal Made Crystal Clear.
Every chapter opens with the gist, draws the hard ideas, and ends with recipes and sources.
Get the book
