> Some may consider the reliance on search a UI failure
No, it's brilliant, in principle. See: spotlight on Mac OS X.
The problem is that Windows Search just doesn't work. I install apps, it can't find them unless they have a start menu enry. I save documents, it can't find them. It does find plenty of irrelevant websites and spurious results from caches, but it misses files sitting directly in my documents folder. Sometimes it returns a result from a partial name hit but when I accidentally type the next character (correctly!) the hit disappears, and it doesn't come back when I remove the offending correct character. It's a mess.
I used to supplement Windows Search with launchy, but then launchy started bugging out. Now I use keypirinha, which intentionally configures bad defaults to encourage you to learn its config file format. Mega cringe. Once you do, though, it does actually work.
Interesting. I’ve never had a problem with desktop search in Win10. It’s all I use and it finds pretty much everything I try. I wonder if indexing issues can end up with vastly different experiences for users.
No, it's brilliant, in principle. See: spotlight on Mac OS X.
The problem is that Windows Search just doesn't work. I install apps, it can't find them unless they have a start menu enry. I save documents, it can't find them. It does find plenty of irrelevant websites and spurious results from caches, but it misses files sitting directly in my documents folder. Sometimes it returns a result from a partial name hit but when I accidentally type the next character (correctly!) the hit disappears, and it doesn't come back when I remove the offending correct character. It's a mess.
I used to supplement Windows Search with launchy, but then launchy started bugging out. Now I use keypirinha, which intentionally configures bad defaults to encourage you to learn its config file format. Mega cringe. Once you do, though, it does actually work.