The control there is in the tracker not the end user.
And this is just giving that user a tracker, they can do the same thing already if they want to.
So we shouldn?t have FTP in IE either? Yes separate can be better because they are more focussed in their development, but integration does have its advantages also.
In general, yes. It makes more sense to integrate FTP with Explorer than IE. It's just a side effect of the way MS designed them all that they end up working together in essentially the same app.
So it was, and now it?s kinda not ?all? about memory.
It never was all about memory, that's just the first thing that comes to mind when someone mentions FF.
As for flexibility, yes it?s beneficial to you and how you work. What about those that just want something simple and that just works easy for them?
It would make more sense, and could be just as simple, to just design a seperate P2P app around the BT protocol than to shove one into FF. And without some central server or tracker it won't work too well because of NAT issues that all filesharing apps have. If both users are behind a NAT device how are they supposed to establish a connection to each other?
So I suppose we should all just have one operating system, one IM client, one make of car?
No, but standards are required for things to work well. The only reason the Internet works at all is because TCP/IP, HTTP, FTP, etc are all open standards. Same thing with cars, there aren't roads that only Ford cars can drive on.
Why have any competitive development at all.
Competitive development is one thing, but can you honestly say that you think the fact that GAIM has to support 8 protocols hasn't slowed it's development at all?
Yes you single out IM development as an example and it has been slightly fragmented development, but they are actually talking of working towards making them basically compatible with each other.
Only since Google has stepped up and started using the Jabber protocol.
Yes they still do the plain old text like they?ve always done, but they?ve added voice, video, file transfers etc all rather seamlessly within the clients.
And each one doing it differently enough so that the others can't work with them. Can you have a video conversation between someone on MSN and someone on AIM?
A good point, but it may have been much harder to develop for considering the number of clients like you said.
Not at all, they would have the exact same advantages and problems just without the dependency on FF. People will still have to download and install the FF extension and they'll still have to setup 'buddies' to share them with on whatever network the extension requires.
Think of it more simply and you'll maybe see one or two advantages that can be developed on.
But how is it more convenient than sharing a file via AIM or GoogleTalk? The BT protocol was designed to get high transfer speeds by spreading the load across all of the peers, if you're limiting your transfers to a handful of predetermined peers you're wasting the main benefit of the BT protocol.