The article itself is great though. I use qBittorrent and I run it in dark mode. I'm going to skip this version for now.
qBittorrent was already quite ugly, but this is just awful: https://github.com/qbittorrent/qBittorrent/issues/18078#issu... — why that bright blue on top of white? If you really want to make it blue, at least retain a decent contrast. And let's not even start with those icons... The shapes could work, albeit they are quite unrefined, but the garish colours do not convey any information nor show any artistic consistency.
(cue the "it's open-source, if you don't like it fork it, but dare not criticize us because it's rude" comment)
I am fine with people not being good at design, but the worst designers are convinced they are decent enough. It's like that law that eludes me right now, that people bad at something often overestimate their abilities and are blind to their shortcomings.
“If you don't like it, fork it” (or a little less polite “if you don't like it, feel free to fork off”!) is perfectly valid IMO. The second part should just be “don't criticize rudely”.
They have no moderation in issues (hence 2.6k+ open issues);
Commiting frequency is (relatively) low for such a complex program;
And it also has lots of odd UX issues that has been solved on uTorrent at least 10 years ago. My pet peeve is that if you have "add .!qd to unfinished torrent files" option enabled, it somehow would prevent you to manually put completed files in and ask QB to re-check, a practice I often do to help seeding with files I already have (if you do so, it either totally ignore it when checking, or delete your completed file!)
I can't really tell why (lack of contributors, or just bad management), so I won't point fingers.
On the other hand, despite all the quirks and issues, the main functions work solid; and they seem to add/improve core features steadily. So I really have nothing to complain as a user. I just avoid updating to newest version in general.
https://datalars.com/2023/01/03/qbittorrent-v450-the-hitchhi...
The reply: It's all going to be fixed in 4.5.1 anyway.