1 |
On Donnerstag 11 Februar 2010, Stroller wrote: |
2 |
> On 11 Feb 2010, at 00:01, Jörg Schaible wrote: |
3 |
> >> ... |
4 |
> >> your understanding is wrong. Completely wrong. Seriously it hurts. |
5 |
> >> |
6 |
> >> start here: |
7 |
> >> |
8 |
> >> http://en.wikipedia.org/wiki/NEPOMUK_(framework) |
9 |
> >> |
10 |
> >> and then proceed with the links. |
11 |
> >> |
12 |
> >> google-desktop is something completley different (and something |
13 |
> >> that can |
14 |
> >> be replaced with find, locate and grep). |
15 |
> > |
16 |
> > Well, in 4.3.x I eliminated it after the first try, because it took |
17 |
> > so many |
18 |
> > resources of my machine, that I could not use it for something else. |
19 |
> > So, you |
20 |
> > mean, in 4.4.x it takes only a 10% of the resources it took with |
21 |
> > 4.3.x? LOL, |
22 |
> > although I really like the idea of the semantic desktop, I rather |
23 |
> > have a |
24 |
> > usable machine ... |
25 |
> |
26 |
> I don't use KDE, but when I freshly install Mac OS (or migrate to a |
27 |
> new hard-drive) the Spotlight indexing hammers the drive for several |
28 |
> hours. It is not reasonable to compare performance during this initial |
29 |
> indexing period. |
30 |
> |
31 |
> There is no way the likes of `find`, `grep` and `locate` - useful as |
32 |
> they are - can operate as efficiently as this kind of indexing (and |
33 |
> Spotlight is pretty damn poor - your KDE implementation is surely |
34 |
> loads better). I love `find`, `grep` and `locate` - they're fantastic, |
35 |
> but my typical usage of them is to perform strict batch operations. If |
36 |
> I just want to open a document then why would I wait for `find`, |
37 |
> `grep` - or go hunting around manually in sub-directories of sub- |
38 |
> directories - when I can just type a keyword into the search box and |
39 |
> find it immediately? |
40 |
> |
41 |
don't forget that updatedb is hammering your harddisk regularly too - and it |
42 |
doesn't just index new files. Nope, it goes over the whole disk. |