t is written in Ruby, and Ruby doesn't come standard with a non-blocking HTTP client. You'd have to pull in EventMachine which would have a far greater cost than spinning up a thread. Additionally, threads in Ruby are user-level threads, so the overhead is a lot smaller than a kernel thread.

I see what you're saying here, but given that t had little other choice, I don't see how this comment adds any value other than to attempt to point out anything that could possibly be wrong with t.

Instead, I think t is fantastic. The usage of threads is good enough, and I thank Erik for spending so much time on a sweet little utility.