Hey, everyone!
I’ve developed a software for file transfers.
I’d love to hear your thoughts on its speed.
If you’re interested, check it out on GitHub.
When advertising a project it helps if you explain why its different and better then existing solutions. Can you do that here please?
1 Like
The following technologies were used in this project to achieve speeds significantly faster than other software:
- 1MB Fragmentation
- Asynchronous multi-threaded sending
- TCP for stability
Using these technologies, I was able to transfer 3GB in just 5 seconds.
Is that for a single file? How do you compare with lots of small files?
How does that compare to using scp and rsync on the same files and between the same hosts?
1 Like
This software, currently designed for single file transfers, is not ideal for transferring multiple files.
Here’s a comparison:
| Feature | This Software | Other |
|---|---|---|
| Fast Transfer | G | Y |
| GUI | Y | ? |
| Support | N | Y |
| Multiple File | N | Y |
G: Great
Y: Yes
N: No
?: Unknown
I use scp and get the full speed of my 1G network already.
Certainly, the scp command is also quite fast.
However, an important point to note is the presence or absence of a GUI (Graphical User Interface).
Let me share the story behind why I created NextDrop.
I noticed that macOS’s AirDrop wasn’t as fast as its name implies, so I started wondering if I could develop an even faster file-sharing tool myself. That’s how “NextDrop” came to life. NextDrop boasts impressive performance, capable of transferring a 3GB file in as little as 5 seconds at peak times, far surpassing AirDrop in speed.
However, something was missing—yes, a GUI. By adding a GUI, I significantly improved usability, allowing users to operate the tool intuitively.
And so, NextDrop was born.