On Sun, 12 Feb 2012 11:24:11 -0800 (PST) Darrell Anderson <humanreadable@...> wrote: > They could have (and still can) accomplished another coup by > redesigning the three backend technologies to be truly optional. I could be wrong but Akonadi's goal seems to be to simplify kdepim data storage by using a standard DB engine that "just works" instead of custom application-specific and mutually-incompatible DB-like code. If it works, everything's fine and we will benefit from advanced optimisations of SQL engines. And from my own experience it finally works in KDE 4.8. NEPOMUK and Strigi don't have the same place, their role is to eat CPU cycles and disk bandwith until the user either deactivates them or does something useful with them. But kdepim won't depend on them.