Picked up this comment from over here:
tauw.comQUOTE
The most obvious one is that it seemed to lack the endgame mode, in which bittorrent tries to get the last pieces from more than one person, so you don't have to wait for the slowest one. A look in the release notes shows that he fixed that in mid february. The way it connected to other peers also lost against the original bittorrent in the 2 tests I made.
Moreover claiming "Bits on Wheels is the first 100% Native BitTorrent client" shows that the implementor has no idea how complicated and hard good networking and p2p is. If you listen to the talk mentioned above, then you'll see how much caveats and problems there are. And bram is doing this like forever. There are many subtleties in his algorithm, that make them work the way it does. A good time investment would be to improve the bittorrent in the areas already identified.
BitsOnWheels may get level to level with azureus some time. But even azureus does not achieve the throughput of the original python client. Which btw just got updated to 4.0.1 with again serious improvements.
I'd love to see people that put this litte python core into a nice really good GUI client, instead of reinventing the wheel and sucking at it.
I too like some others in this thread wish the official client was up-to-date. I have no idea on programming etc and have tried to build the official python source (4.0.1) but it doesn't appear to have worked correctly, as in this previous Neowin thread:
Compiling Python Source