A command-line power tool for Twitter
github.com
A command-line power tool for Twitter
1–10 of 14 posts
Re: A command-line power tool for Twitter
#2That's not what threads are about.
Re: A command-line power tool for Twitter
#3Re: A command-line power tool for Twitter
#4"Multi-threaded: Whenever possible, Twitter API requests are made in parallel, resulting in faster performance for bulk operations." That's not what threads are about.
Re: A command-line power tool for Twitter
#5Re: A command-line power tool for Twitter
#6"Multi-threaded: Whenever possible, Twitter API requests are made in parallel, resulting in faster performance for bulk operations." That's not what threads are about.
Why not? Thread pools are great for doing bulk operations... long API requests is a great thing to do in parallel when possible.
Re: A command-line power tool for Twitter
#7This has many cool features and is easy to use in scripts but if you just want Twitter in your terminal, check out Twirssi[1]. It plugs into irssi which many have running already anyway. [1] http://twirssi.com/
Re: A command-line power tool for Twitter
#8Earlier quoted context omitted.
Why not? Thread pools are great for doing bulk operations... long API requests is a great thing to do in parallel when possible.
There's a runtime overhead of spinning up a bunch of threads that are just going to sit idle waiting for an API response. There are better asynchronous models for that sort of thing.
Re: A command-line power tool for Twitter
#9Re: A command-line power tool for Twitter
#10"Multi-threaded: Whenever possible, Twitter API requests are made in parallel, resulting in faster performance for bulk operations." That's not what threads are about.
Why not? Thread pools are great for doing bulk operations... long API requests is a great thing to do in parallel when possible.
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.