One break, two outcomes
The same single break in a knit and in a weave. In the knit nothing holds the loop above the break, so the failure climbs the wale; in the weave every other thread is still held by the threads crossing it, and one thread comes loose.
4 essays call
run. The drawing above is what it returns with no arguments at all; every
call below passes it something, because a placement that passes nothing draws whichever
member of the family the generator happens to default to rather than the weave its essay
argues about.
Where it is called
Changing this generator changes every one of these figures.
Ravel, fray and run
Cut a woven cloth and one thread comes loose. Break one loop in a knit and every loop above it follows. The two structures fail in opposite ways, and the reason is topology rather than strength.
Warp knitting, which is a different thing entirely
Every wale has its own thread, and if the thread never leaves its wale the fabric is a set of independent cords. Whether a lapping makes cloth is decided by a coprimality condition — the satin theorem, in a knit.
A cloth does not mind a hole
A hole in a film costs it two thirds of its strength whatever the hole's size, because a continuum concentrates stress at an edge. A cloth's threads carry their own load and hand almost nothing to their neighbours, so a hole costs exactly the threads it removes — a loss that is linear in the hole, independent of the sett, and zero for a slit along the load.
A run is a race between two energies
A dropped stitch travels when a loop can be pulled out of the loop below it, and there are two candidate drivers: the energy the loop releases by unravelling, and the load the garment is under. One of them turns out to be negligible, and knowing which changes what a knitter can do about it.