Agreed. And many people search using their built-in browser functions anyway so Google Suggest won't really kick in at all (e.g. I search from Konqueror's address bar).
As an aside, Google Suggest crashes my browser (Konqueror 3.3.1).
I like the KDE apps too (I use Konqueror and Kopete regularly for my Internet needs), but I run them in Ion2. You don't have to put up with the extra stuff (Kicker and KDesktop, for instance) and still be able to use the KDE apps.
If every single department shared their information with every other department, wouldn't there be information overload? I don't think bandwidth is infinite...and even if it was, the people are still human and can only process so much information at a time.
If P2P is implemented on a department-by-department basis, information overload will be reduced, but some of the benefits (e.g. increased collaboration) will be negated. Ditto if P2P is implemented on even smaller scales (sub-department).
If I recall correctly Groove stores all its information on client nodes, and I believe each node caches the information on other nodes. This would create another problem with respect to information overload...hard disk space, memory for database indexes etc.
Slashdot Mirror
Agreed. And many people search using their built-in browser functions anyway so Google Suggest won't really kick in at all (e.g. I search from Konqueror's address bar). As an aside, Google Suggest crashes my browser (Konqueror 3.3.1).
I like the KDE apps too (I use Konqueror and Kopete regularly for my Internet needs), but I run them in Ion2. You don't have to put up with the extra stuff (Kicker and KDesktop, for instance) and still be able to use the KDE apps.
If every single department shared their information with every other department, wouldn't there be information overload? I don't think bandwidth is infinite...and even if it was, the people are still human and can only process so much information at a time. If P2P is implemented on a department-by-department basis, information overload will be reduced, but some of the benefits (e.g. increased collaboration) will be negated. Ditto if P2P is implemented on even smaller scales (sub-department). If I recall correctly Groove stores all its information on client nodes, and I believe each node caches the information on other nodes. This would create another problem with respect to information overload...hard disk space, memory for database indexes etc.