> > After the time comes when we can rely on nepomuk 24/7, we can remove > > the caching kded service since all of this is hidden behind the API. > > if we work around subsystems because "they don't work well yet" then the > odds they ever will work well goes down as there is less reason / > motivation to get them working well. if those subsystems can't be made to > work well, then we shouldn't have them in our stack. otherwise, the aim > should be to make them work. it's that simple. please stop working around > brokenness.
erg. while you're right... my desktop has already developed a tendency to fall half to pieces when nepomuk goes down. or maybe it's dbus having trouble, I'm not 100% certain, but in any case we've gotta get those subsystems working *first* because if I have to reboot my computer every couple of days to keep it working-ish I'm going to throw it out the fucking window. oh crap I'm late for school now byebye -- This message brought to you by eevil bananas and the number 3. www.chani3.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel