Funny future ajax assumption

I got a kick out of this idea, thought you guys might too:

<blink> timing For a long time, the ignoble <blink> tag seemed destined for all the one-hit wonderness of a Vanilla Ice or an MC Hammership. Loved for a month or two, then cast aside with nought but the occasional fond memory. Yet in an unanticipated turn of events, intrepid developers have recently been asking hard questions about <blink>. “If it was really as dumb as people make out, why was its timing so precise?” asked one Ajax guru who wished to remain anonymous on the grounds that he had been consuming Red Bull for the past eight hours. Another guru in questionable state pointed out “setTimeout() isn’t all that! Did you ever try it in lynx? Total no-op!” And so it was that <blink>'s true purpose became known. Reborn as much out of frustration with setTimeout as it was with the promise of a more robust solution. No longer eye candy, but a super-precise timing mechanism. The thinking geek of 2007 embeds a single <blink> tag on the page, hides it with CSS, and arranges all application scheduling against the swift oscillations of this postmodern crystal timer.
Purchase Intent Data for Enterprise Tech Sales and Marketing | TechTarget
Who the hell comes up with this crap?