Live data from Hacker News

A command-line power tool for Twitter

github.com

1–10 of 14 posts

Re: A command-line power tool for Twitter

#4
post #2

"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

#5
yes, please! have needed a tool to help deal with unfollowing some folks for a while, i am always at follow limit, and when you're in the ui follow list it starts with the people who tweet the most and who you interact with the most afaict, so i end up scrolling for ages trying to find anyone uninteresting. people seem to show up multiple times in infinite scroll, too, so it's like digging a fucking hole in sand.

Re: A command-line power tool for Twitter

#6
post #4
post #2

"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.

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

#7

This 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/

Using bitlbee for this is awesome aswell. Then you don't need to run several scripts for more functionality (g+, Facebook, jabber etc)

Re: A command-line power tool for Twitter

#8
post #6
post #4

Earlier 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.

Unless you plan to open 10K connections to twitter, for a small utility like that, it hardly matters.

Re: A command-line power tool for Twitter

#10
post #4
post #2

"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.

No, long parallel requests are great to do concurrently on a single thread. A thread is a computation primitive, you spin off a thread when you want to compute many things at once, not just wait for many things at once.

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.

Post reply on HN