Re:What software engineers should know about search (2017)
by ratherbefuddled on Monday October 18, 2021 @08:15AM
(#28904620)
Given the state of search functionality built into websites I use often I can only imagine you have a very heavily curated list.
In my experience so many sites have searches that return bad results, restrict your ability to see a list of results due to some poorly thought through typeahead functionality, or simply do not work without third party scripts and cookies that I often resort to "site:<domain>" in ddg or worse, google.
I find hierarchical indexes only of marginal use when looking for information. I can only know where in the hierarchy something is if I'm very familiar with the website - because many things could logically be in more than one place.
Re:What software engineers should know about search (2017)
by matheusmoreira on Monday October 18, 2021 @08:27AM
(#28904683)
> organized, hierarchial index
Yes!!
So many blogs without a list of posts in chronological order. So many sites without a list of pages. So annoying.
Re:What software engineers should know about search (2017)
by sriram_malhar on Monday October 18, 2021 @05:26AM
(#28903655)
Would it bother you if foo.com took your query and send "query site:foo.com" to google? The results would be foo.com specific.
Re:What software engineers should know about search (2017)
by hihihihi1234 on Monday October 18, 2021 @05:38AM
(#28903723)
I often find this gives better results. Eg I'm much likely to find what I'm looking for if I search for "(query) site:reddit.com" than if I use reddit's own search feature.
Re:What software engineers should know about search (2017)
by hihihihi1234 on Monday October 18, 2021 @11:59AM
(#28906912)
Much more likely*
Granted, a lot of sites out there that provide a search function do not necessarily need one, and would instead benefit from an organized, hierarchial index. With these types of websites, using the search function only adds unnecessary friction.