|
It is mind-boggling, how in this day and age search functions can still be soooo bad in so many places on the web and inside applications. At the very least a 100% substring match should be very visible in the result. If not at the top, then there should be sorting criteria, to make it appear at the top, so that one can sane-ify the search result, when it is not sane. A good example for bad search is the windows start menu. If you just logged in and the system is still loading (whatever it is doing all that long...) and you press the super key and then start typing, it might be too slow to find things _locally on your disk_, and might start searching online. When you have developed an automatism and just continue typing and then hit enter/return key, you will get some online shit result shown in Edge or some Microsoft store shit, instead of simply launching your already installed app. A critical race right there in the start menu. It's baffling. Recently, there was a reddit post about a KDE menu search thing just as silly. It would not prioritize the title/name of an app, but instead, after typing 3 or more characters, find a word in the description of a launcher/starter of other apps and show those first, even though the 3 chars or more are a perfect substring of the name of an app. People reinvent simple search and make silly searches over and over again. One of the main criteria is, that a substring match must lead to being high in the results, if not the top result. Shorter wins vs longer, because the match has higher percentage of match with the full title/name. Beginning of the string matched? Higher in results. All very basic things, that shouldn't be difficult to implement. |