That's not what threads are about.
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.
If you would spin up threads just for this you're wasting memory and slowing down startup time.
And if you would destroy the threads and spin them up again for every batch of API calls, the result may counterintuitively be a slower app due to the overhead of creating the threads themselves.
At the same time concurrency is free. There's no overhead for doing a call async.
I wish Twitter, Inc weren't the absolutely stinking worst maker of Twitter clients. :(
