On 11 Feb 2010, at 00:01, Jörg Schaible wrote:
...
your understanding is wrong. Completely wrong. Seriously it hurts.
start here:
http://en.wikipedia.org/wiki/NEPOMUK_(framework)
and then proceed with the links.
google-desktop is something completley different (and something
that can
be replaced with find, locate and grep).
Well, in 4.3.x I eliminated it after the first try, because it took
so many
resources of my machine, that I could not use it for something else.
So, you
mean, in 4.4.x it takes only a 10% of the resources it took with
4.3.x? LOL,
although I really like the idea of the semantic desktop, I rather
have a
usable machine ...
I don't use KDE, but when I freshly install Mac OS (or migrate to a
new hard-drive) the Spotlight indexing hammers the drive for several
hours. It is not reasonable to compare performance during this initial
indexing period.
There is no way the likes of `find`, `grep` and `locate` - useful as
they are - can operate as efficiently as this kind of indexing (and
Spotlight is pretty damn poor - your KDE implementation is surely
loads better). I love `find`, `grep` and `locate` - they're fantastic,
but my typical usage of them is to perform strict batch operations. If
I just want to open a document then why would I wait for `find`,
`grep` - or go hunting around manually in sub-directories of sub-
directories - when I can just type a keyword into the search box and
find it immediately?
I cannot for a moment believe that you (Roy) can organise your files
so that you can find them easier than typing a search term & clicking
on the correct result. You just don't want to try it because your
current methods are "good enough" for you, but this isn't good grounds
on which to complain about KDE moving on with their development of a
state-of-the-art desktop which will actually make life easier for
millions of other people (people who aren't afraid to try it).
After the initial index, data is only indexed when you save a file,
using inotify [1], which is built into the kernel for maximum
efficiency. (Please correct me if I'm wrong about KDE's
implementation). So in actual real world usage, the result is that it
takes a fraction of a second longer when you save an Open Office
document. My 5 year old desktop can handle this overhead just fine. A
£100 Core 2 Duo + motherboard combo would surely handle it MUCH
better. I trust you can see why I'm dubious of claims of poor
performance.
I don't wish to seem rude, being strident with my arguments here. This
is just the way I see it.
Stroller.
[1] http://en.wikipedia.org/wiki/Inotify
