Linked by Thom Holwerda on Thu 18th Jan 2007 15:11 UTC, submitted by Torsten Rahn
Thread beginning with comment 203113
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: not perfect but still nice
by anda_skoa on Thu 18th Jan 2007 19:19
in reply to "RE[2]: not perfect but still nice"
RE[4]: not perfect but still nice
by superstoned on Thu 18th Jan 2007 19:26
in reply to "RE[3]: not perfect but still nice"
RE[3]: not perfect but still nice
by rayiner on Fri 19th Jan 2007 18:09
in reply to "RE[2]: not perfect but still nice"
RE[4]: not perfect but still nice
by superstoned on Sat 20th Jan 2007 21:53
in reply to "RE[3]: not perfect but still nice"







Member since:
2005-07-07
well, indeed, all these projects are pretty young, so we'll have to wait to see which one will stand out as the best solution. tracker and strigi of course have (imho) the best chance, being reasonably performant and not depending on controversial stuff like mono/java. if both happen to deliver the same d-bus interface, the best will be used the most, and that's the most optimal solution.
btw strigi also delivers database services and is going to be the foundation of meta-data extraction and manipulation in KDE 4, in addition to having Nepomuk (contextual linking, labeling etc) integration, so i think it has the best cards right now... on the other hand, tracker is close to integration in gnome, and even tough gnome mostly doesn't integrate things very deeply (or at least, does so slowly), gnomes don't like stuff smelling kde'ish. after all, they even rejected aRts, even tough it was plain C, had a gnome-lib dependency and was the only technically reasonable solution by then...
but things can change.