Jarvis, an Alfred Alternative for Windows

> Jarvis is currently under development, and all features are not there yet.

Both of those statements are false if what you say is true.

I've never understood why it's performance has been deemed acceptable.

I'm on my phone right now so forgive the random sample, but this gives the gist of its usage. https://stackoverflow.com/a/34340288

The only issue I have seen is when the index corrupts, this was more common in win7, and in our research it was often the result from an over aggressive AV jamming up the process.

But I've written a number of systems that make use of this, and when comparing other ways to accomplish this sort of in depth search, it's the most reliable and manageable.

It does have the caveat that it works best on places indexed by the OS, and adding locations to the indexer via code requires some pinvoke stuff most people aren't comfortable with.

But once you do that the overhead isnt horrible, you do the indexing on change, and results comeback as fast as a typical small query, 10 seconds tops on a typical desktop machine.

We wrote a scheduler that on windows monitored the windows indexer itself, when it kicked off we scheduled it, and trigged it once the system finished.

I don't honestly recommend it over windows search, but if portability, and multi system searching is required it worked great.

But not a task for those who are crunched for time, or lack resolve.

The standard search feature in the start menu is atrocious, at least as bad as it was in Vista and 7. I actually stopped using it years ago, because it just.does.not.work. I honestly don't know how such a terrible feature has been allowed to remain in Windows for so long.

At least from the linked article, it sounds like this might solve the problem - really keen to try it out!