Linked by Eugenia Loli on Tue 11th Jul 2006 07:22 UTC, submitted by Dan Warne
Permalink for comment 142141
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2005-07-22
From the ridiculously brief and lacking in content article, there was one difference that I found rather interesting:
Apparently, the process of Beagle actually indexing a file is exposed in the UI, so you can stop it if you want.
This worries me slightly, I mean, when will the file be indexed again properly? And it also rather suggests the developers have little faith in the indexing being "unobtrusive."
Personally, I think the indexing should be taken of completely behind the scenes. There's no reason why the user should ever have to no what is going on index-wise, in the same way they shouldn't have to know how the hard drive is handling its cache at a particular moment.