April 20, 2026
Stitch, glitch, and FOMO itch
Knitout and Kniterate 3
Code turns to cozy: knit hackers cheer while the lone comment screams tool FOMO
TLDR: Developers got their knitting code working on a Kniterate machine, turning instructions into real ribbed fabric and moving toward automated finishing. The comment section’s mood? Pure maker nostalgia—one standout reply about a missed 3D‑printed chisel roll captured the community’s mix of excitement, pragmatism, and tool‑regret humor.
Knitting nerds and curious onlookers watched code become cloth this week as the team tested their malleable knitting software on a semi‑industrial Kniterate machine. Translation: they wrote instructions, pressed go, and actual ribbed fabric came out. The crew learned two‑bed knitting (think two needle rows working together) and wrangled yarn “carriers” (little guides that feed the yarn) that kept ending up on the wrong side. A hacky fix got the samples rolling, with tidy rib swatches and a push toward automating the final “cast‑off” step (finishing the edge), instead of doing it by hand for 20 minutes. Cue the internet: the biggest mood in the comments wasn’t about stitches—it was maker FOMO. The top (and only!) reply veered straight into “the one that got away” territory, reminiscing about a 3D‑printed kevlar chisel roll. And honestly? It fits. This project sits right on the fault line between hands‑on craft and code‑powered machines, so the vibe split is predictable: pragmatists love the quick hacks that get yarn flowing early; purists cringe at anything that isn’t perfectly elegant. The drama isn’t angry, it’s relatable—half the audience is cheering, half is side‑eyeing, and everyone’s remembering that tool they didn’t buy when they had the chance. Cozy chaos, achieved.
Key Points
- •The team advanced a Knitout-to-Kniterate code visualizer and ran multiple tests on a Kniterate machine at Chelsea.
- •Hands-on training with a Brother ribber improved understanding of 2-bed knitting; a ribber was set up in the studio for further practice.
- •A scripted workflow appended a waste section to a front-bed rectangle, revealing carrier-direction issues caused by a double introduction.
- •Adjustments included deferring “out” carrier statements; this aligns with Kniterate practice and contrasts with Shima-style carrier handling.
- •Two test samples (1×1 rib and fisherman’s rib) knitted successfully; cast-off automation is being adapted using knitout-frontend JavaScript.