4 ms·

This mentality "lets add a daemon to run in background 24/7" to provide some service thats sits mostly unused is unacceptable. Its not only gnome developers, it

• digi_owl 8y ago
  What is going on as of late, and it is led by Gnome/freedesktop/RH devs, to split fully working software into two parts. A UI frontend, and a deamon backend. And between them sit dbus and polkit, so that someone, somewhere, may write some "fine grained policies" about who can and when they can do anything. What i am observing is that what used to be a "clean" system once you got used to the unix thinking, is being torn to shreds trying to placate two sub-groups. The first is the military-industrial complex that wants to make damned sure the grunts can't read how crap the "police action" is going. The second the the cloud-heads that wants everything to be able to scale from 1 to 1 million running units with the push of a button.
• cryptonector 8y ago
  If such a daemon does not use cycles unless called out to, then the only problem is that it's one more attack vector. Oh wait.
  • nisa 8y ago
    not sure if it's still a thing but akonadi / baloo on kde manages to even saturate slower sata-ssd random io and fills a mysql database. Lot's of fun if you have several kernel tree / buildroots laying around in your home. baloo also really likes to segfault when parsing content and is not sandboxed afaik. I really like KDE but this part is sadly a good in theory but pure pita in practice.