libtorrent-rasterbar has (had?) a lot of problems stemming from its complex C++ codebase and Boost dependency. The painful and protracted v1 -> v2 migration was the main visible consequence.
No proper client/daemon (thus core/GUI, code is Qt-ware) separation with a clean transmission-like RPC.
As a long time transmission user, I've felt exactly the opposite. They have been slowly falling behind other clients. They still don't have torrent v2 support even![1] It took them many years to implement sequential downloading.[2]
As someone following its development closely, Transmission botched its v3 -> v4 transition by underestimating the difficulty of keeping regressions under control when doing a simultaneous C -> C++ rewrite and adding features.
PS: not convinced by rtorrent's "recent" revival, the general trend in its issue tracker screams "not stable" to me; and still no clean client/daemon, like Qb. I say that as an old rtorrent-pyroscope user that still remembers the horrible config format that made customizing Quake 3's CVARs intuitive.
8 comments
[ 2.6 ms ] story [ 32.6 ms ] threadNo proper client/daemon (thus core/GUI, code is Qt-ware) separation with a clean transmission-like RPC.
1: https://github.com/transmission/transmission/issues/458#issu...
2: https://github.com/transmission/transmission/pull/4795
My advice? Continue to use Tr3 via https://github.com/stefantalpalaru/transmission-og with spoofed PeerID and keep an eye open on the other clients.
PS: not convinced by rtorrent's "recent" revival, the general trend in its issue tracker screams "not stable" to me; and still no clean client/daemon, like Qb. I say that as an old rtorrent-pyroscope user that still remembers the horrible config format that made customizing Quake 3's CVARs intuitive.