็™ป้Œฒใ—ใฆๆ‹›ๅพ…ใƒชใƒณใ‚ฏใ‚’ๅ…ฑๆœ‰ใ™ใ‚‹ใจใ€ๅ‹•็”ปๅ†็”Ÿๅ ฑ้…ฌใจ็ดนไป‹ๅ ฑ้…ฌใ‚’็ฒๅพ—ใงใใพใ™ใ€‚

Guillermo Rauch
@rauchg
ๅ‚ๅŠ  July 2008
662 ใƒ•ใ‚ฉใƒญใƒผไธญ    920.3K ใƒ•ใ‚กใƒณ
If your terminal ever gets into a 'bad state', like garbled outputs, you run ๐š›๐šŽ๐šœ๐šŽ๐š. I noticed it wasโ€ฆ oddly slow. Turns out in 1979 3BSD's ๐š๐šœ๐šŽ๐š had a ๐šœ๐š•๐šŽ๐šŽ๐š™(๐Ÿท) to let mechanical printer-and-ink terminals 'settle down' ๐Ÿ˜‚ I asked ๐š๐šก to write me a faster alternative in Zig. It takes 1ms instead of 1s. It was really cool to dive deeper into ๐š—๐šŒ๐šž๐š›๐šœ๐šŽ๐šœ, ๐š๐šœ๐šŽ๐š, ๐š๐šŽ๐š›๐š–๐š’๐š—๐š๐š˜, and the myriad ways in which your terminal can getโ€ฆ cursed. It's legit fascinating how far back our technology stack goes, and how enduring good system design is, even with the occasional 'spider webs' you can find. Check out for a fun explainer (and some alternative solutions.) ps: once you start using ๐š๐šก, you'll notice slowness like this everywhere :D
ใ‚‚ใฃใจ่ฆ‹ใ‚‹