@JohnTHaller
Thanks.
@Midas
Halite & Tixati
For me
Halite is very unpolished, just maximize the window and you will see what I mean. About
Tixati- I don't find anything alien about it (some time ago I switched from light background to default dark background):
I do not think that any torrent client should look like
uTorrent or
Transmission. In terms of resources usage
Tixati uses about the same memory as
qBittorrent but in terms of customization in my opinion it can only be compared to bloated and heavy
Azureus/
Vuze/
BiglyBT. Just look at properties:
and at settings:
For me
Tixati is a masterpiece. The only annoyance is that it rarely (once in about month and a half) shows a donation pop-up.
Transmission
As I stated in my previous post, the official Windows version is still very much based in the Qt framework.
I disagree:
There are several transmission clients for different operating systems including Unix-like, macOS and BeOS/ZETA. Each operating system front-end is built using native widget toolkits.[7] For example, transmission-gtk uses the GTK+ interface, transmission-qt the Qt interface, and transmission-cli a Command-line interface. Transmission-remote-cli is an ncurses interface for the transmission-daemon. Python-transmissionrpc is a Python module implementing the JSON-RPC client protocol for Transmission
On Windows, Transmission-Qt can be built with MinGW,[23] the daemon and console tools can be built with Cygwin,[24] also there are two third-party GUIs: transmission-remote-dotnet[25] and Transmission Remote GUI,[26] as well as unofficial full builds of Transmission's Qt Client.,[27][28] There is also an unofficial full build of Transmission daemon which can be run as a Windows service.[29] This same unofficial full build of Transmission daemon running as a Windows service can be used for direct streaming of the downloading file(s).[30]
(Source -
Wikipedia)
The developer of the unofficial and discontinued fork called it
Transmission-Qt just to differentiate it from the official
Transmission which at the times of
Transmission-Qt development didn't offer a stable windows version. Now
Transmission-Qt is gone and even it in the "About" it showed just
Transmission, screen:
In short- now there is only one official
Transmission client which is called
Transmission and it uses different frameworks for different OS. Unofficial fork
Transmission-Qt is long gone. Since now
Transmission has official Windows version it is misleading to call it
Transmission-Qt, it is just
Transmission, screen:
There are two other nuisances besides the lack of official portable version for Windows that make
Transmission repellent to me- the Windows Installer and the poor usage of GitHub for
releases- I ascribe it to negligence rather than to ignorance.