On Mon, Apr 28, 2014 at 2:36 PM, Luca Beltrame <lbeltrame@kde.org> wrote:
If Baloo was that toxic to everyone's computer, why people did not test it in advance? I can understand that not everyone is supposed to test beta software,
I test things with KDE on an isolated test machine.... when I can. I don't test every release. The 4.12.99 release did land on my test machine for a day or two, but... I never noticed Baloo. I had not realized that the former search... Nepomuk... was being 100% replaced now that it was... you know, working OK. The info about Baloo may have been posted on the ML, but it's clear most of us missed it. Lots of excuses... persona life, too many emails etc etc.
Since the new search system was introduced, in the first beta, I wrote to the mailing list asking the brave to test it to ensure we had a smooth experience later on. Aside the openSUSE KDE team and a few others, no one did. How can you fix something that you do *not* know it's broken?
Why was Nepomuk removed? Was was Baloo invented? I still haven't quite figured this one out. If I test something, I test it on an isolated system on my LAN. It doesn't touch my NAS. It doesn't touch my internal data storage on my main machine. So... any indexing Baloo did was on an empty home, with no additional external drive mounts. Basically.. nothing to index. That said... when Baloo was enabled on my primary system, it indexed a 2TB NAS, a 1 TB mechanical and a 250GB SSD in just a few minutes. That's photos, videos, documents, VM images etc etc. The only I/O hit I had was to the NAS, but that's not unreasonable given the network speed and the hopelessly slow NAS I've got. Hardware is an AMD Quad core (965), 16GB RAM on a Gigabye MB. On my particular setup, there was next to zero I/O impact. Why would that be the case on one install, but the next just falls over flat?
It really makes me bitter to think that all that it was tried to do to ensure that reports could be caught in time to ensure a better user experience was all for *nothing*, and only later the complaints (and nothing else, almost) arrived.
On that point... one.. just one single addition to Baloo would have alleviated 99% of the kerfuffle (or.. is it hullabaloo?). A simple on/off toggle that set the true/false option in the baloorc file would have been all that was necessary here. The people who don't want indexing could have simply went click and it would have not been an issue. Or better yet... make it an opt-in with a first start popup that says hey, cool new feature can be enabled here. C. -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org