[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Baloo] [Bug 331932] add option for disabling indexing
From:       <boblovgren55 () gmail ! com>
Date:       2014-05-05 18:16:25
Message-ID: bug-331932-17878-3GgBCcaubx () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=331932

--- Comment #51 from boblovgren55@gmail.com ---
" Making the decision to effectively try to force all users to then accept the
default and remove the ability to switch off desktop search with a simple
switch was perhaps already likely to alienate users."

Nepopuke already had a feature with a switch to enable or disable search
functionality. If alienation were to occur, don't you think it would've
occurred back then and users would have already gotten it out of your system?
Your logic makes zero sense. Speaking of flame wars, maybe that's what needs to
happen. I do not want this "feature" foisted on me, and neither do numerous
other users. This is not Windows; if someone wants to remove Baloo packages
entirely, then that should be possible. Even Windows doesn't suck the amount of
CPU and disk I/O that Baloo does upon initial boot. On a Windows machine, you
don't even notice that it's indexing. My point here is that Baloo is a poorly
coded program, and because of that and because of it's performance
implications, it should be able to be disabled, removed. Baloo is probably the
worst part of KDE that I have ever seen in all my Linux years, and the file
cleaner infinite loop bug is _not_ fixed; it still took up 100% of 1 core for
endless hours doing _nothing_, and this was after 4/22.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]