Limbo argues that suffering is not a consequence of play but its actual medium.

You don't die in Limbo to learn what not to do — you die because dying is the game's only feedback system.

The saw trap doesn't teach caution; it teaches that your body crossing its threshold is data, and data accumulates into progress. Each death is graphically precise, violent, immediate — the boy's limbs scatter, his head rolls separate — yet the game doesn't make you feel bad about this, it makes you indifferent to it.

You restart at the last checkpoint, which exists to optimize your suffering rather than spare you from it. This is the hidden architecture: failure has been repackaged as iteration, and the game whispers that there is no shortcut, only accumulation — that if you die forty times to a puzzle, those forty deaths were not wasted time but the actual cost of understanding. Productivity culture absorbed this logic wholesale, so productivity gurus now call failure "learning" and suffering "growth," while therapists speak of "processing grief through iteration" and self-help books promise that each humiliation is a data point toward your authentic self.

Limbo didn't invent this machinery, but it formalized it and made visible how a system could function perfectly while treating human failure as its fuel. The game understands what Silicon Valley only pretends to: if you can make people feel like their pain is productive, they will generate it infinitely, for free.