I am against Torrents being added in surge downloader.

[SuperCoolPencil]

I am against this feature being added in surge downloader. heres my reason below

• it makes surge complex. these are different file transfer protocol. best download manager in the world is IDM and they dont have it as well. they solely focused on making the download manager feature rich
• it will be half baked unlike qbittorrent, deluge, rtorrent, transmission etc. it cant be as good as them. which torrent downloaders use day to day life
• adding to the previous point, torrent GUI(TUI) is different than regular downloader. you cant make it feature rich and complex as it will ruin downloading experience for both. this is a design limitation
• Integration becomes another issue. you will need addons/extension for browser, link capture. default application will cause headache having 2 or more torrent browsers
• hard to be acknowledged by private trackers. theres a good chance it wont be allowed as top tier private trackers require precise stats
• bittorrent protocols requires additional user specific task like seeding, cross-seeding/renaming, ratio management, partial seeding, storage management etc

i can speak these from 20+ years of experience having used different protocols (from ddl, private trackers, usenet, soulseek etc). Currently i am using FDM and they are stuck with same issue.

I recommend keeping downloader and torrent client separate. like create another TUI app called surgebt. it will give you UX/UI freedom which will solve a lot of future headache and complexity. I am sorry i have not communicated these concerns earlier

Originally posted by @sfzaw in #326 (comment)

[SuperCoolPencil]

Hey @sfzaw Thanks for putting up this point. I created this new issue so we could have a better discussion and not flood the PR with comments...

[TPG1000]

I recommend keeping downloader and torrent client separate. like create another TUI app called surgebt. it will give you UX/UI freedom which will solve a lot of future headache and complexity. I am sorry i have not communicated these concerns earlier

This would be my suggestion too. This seems to fit better with keep the TUI clean. Then when stable and 'Surge Core' becomes a thing it'll act like a plugin: Surge TUI, Surge GUI, SurgeBT.

Feature creep stops things being good. At the moment we have a good TUI but why have 3 average functions when 1 good one makes more sense.

[junaid2005p]

I agree currently we are focusing on making surge stable. We still have a considerable amount to do. When the surge TUI app is stable we will extract surge core and then other apps can be built on top of it.