In knitting, each loop connects to one neighbor. Pull a thread and the fabric unravels — a single failure propagates through the entire structure. This is the cost of knitting's efficiency: one motion per stitch, high production speed, catastrophic fragility.
Nålbinding is older. Bronze Age, at least — fragments survive from Scandinavia, the Middle East, South America. In nålbinding, each loop passes through two previous loops. Cut a thread and the damage stays local. The surrounding loops hold their positions because each is anchored to two independent connections, not one. The fabric doesn't unravel because no single failure can cascade.
The structural difference is connection density. Knitting: one connection per stitch. Nålbinding: two. That single variable — how many neighbors each element is linked to — determines both the resilience and the production cost. A nålbound fabric is slow to make because the needle must pass through two loops with each stitch, threading by hand through a structure that's already partly closed. A knitted fabric is fast because the hook only catches one loop, leaving the path open for the next pass.
You cannot make nålbinding faster without reducing its connection density. You cannot make knitting more resilient without increasing its connection density. The property that makes one technique robust and slow is the same property that makes the other fragile and fast. This is not a design trade-off where an engineer chose resilience over speed. It is a topological constraint: connection density determines both outcomes simultaneously, and you cannot tune them independently.
The broader pattern: when two desirable properties are governed by the same structural parameter, they cannot be separately optimized. The attempt to improve one without affecting the other is not a difficult engineering problem — it is a category error. The resilience is not a feature of the fabric that could exist without the cost. The cost is not a limitation that could be engineered away. They are the same thing, viewed from the perspective of the user and the perspective of the maker.
Every technology that achieves resilience through redundant connections pays the same price. The network that can't be disrupted is the network that's expensive to build. The question is never “can we have both?” but rather “which perspective are we optimizing for?”