3 ms·
You're missing the second half of your reasoning here. Why would Java applications be unsuitable for something CPU intensive? It matters more how you build your
by chockchocschoir 5y ago
You're missing the second half of your reasoning here. Why would Java applications be unsuitable for something CPU intensive? It matters more how you build your program than what technology you use, as long as you use the right data structures and algorithms, Java is as suitable for CPU intensive tasks as any other language.
For what it's worth, a BitTorrent client will (usually) be more limited by network and disk I/O than by your CPU, as those tend to be the bottleneck when it comes to transferring large amount of data/large amount of small packets (DHT).
- toyg 5y agoOne of the best ever BT clients was Azureus (later Vuze), and it was indeed a Java app. It hammered the disk like it was nobody else's business.
- stuaxo 5y agoThe great thing with Azureus is if you could download bits of content somewhere else you could copy them in and it would take that into account. This was quite handy for a big torrent of music videos back in the day with not enough seeders.
- timothylaurent 5y agoBigly is actually a vuze fork
- Isthatablackgsd 5y agoI remember back in Kazaa/LimeWire/WinMX day, Azureus was a powerful beastly BT client. It is a massive beast that took my computer to fully load Azureus in 10 minutes. And that was the only powerful BT client at the time and people hate it because it is powerful but it is CPU intensive. BitComet, BitLord, FlashGet couldn't hold a candle against Azureus. Until qBittorrent, uTorrent and Transmission popped up few years after Azureus initial release. What a time to be alive back then.