“Intended” is a weird choice there. Certainly the people selling them are selling them as search engines, even though they aren’t one.
On DDG’s implementation, though, you’re just wrong. The search engine is still the search engine. They are using an LLM as a summary of the results. Which is also a bad implementation, because it will do a bad job at something you can do by just… looking down. But, crucially, the LLM is neither doing the searching nor generating the results themselves.
Maybe I just don’t know what “generating results” means. You query a search engine, and it generates results as a page of links. I don’t understand how generating a page of links is fundamentally different from generating a summation of the results?
Its a very different process. Having work on search engines before, I can tell you that the word generate means something different in this context. It means, in simple terms, to match your search query with a bunch of results, gather links to said results, and then send them to the user to be displayed
The LLM is going over the search results, taking them as a prompt and then generating a summary of the results as an output.
The search results are generated by the good old search engine, the “AI summary” option at the top is just doing the reading for you.
And of course if the answer isn’t trivial, very likely generating an inaccurate or incorrect output from the inputs.
But none of that changes how the underlying search engine works. It’s just doing additional work on the same results the same search engine generates.
EDIT: Just to clarify, DDG also has a “chat” service that, as far as I can tell, is just an UI overlay over whatever model you select. That just works the same way as all the AI chatbots you can use online or host locally and I presume it’s not what we’re talking about.
I had to tell DDG to not give me an AI summary of my search, so its clearly intended to be used as a search engine.
“Intended” is a weird choice there. Certainly the people selling them are selling them as search engines, even though they aren’t one.
On DDG’s implementation, though, you’re just wrong. The search engine is still the search engine. They are using an LLM as a summary of the results. Which is also a bad implementation, because it will do a bad job at something you can do by just… looking down. But, crucially, the LLM is neither doing the searching nor generating the results themselves.
What do you mean its not generating the results? If the summation isn’t generated, wheres it come from?
I dont want to speak for OP but I think they meant its not generating the search results using an LLM
Maybe I just don’t know what “generating results” means. You query a search engine, and it generates results as a page of links. I don’t understand how generating a page of links is fundamentally different from generating a summation of the results?
Its a very different process. Having work on search engines before, I can tell you that the word generate means something different in this context. It means, in simple terms, to match your search query with a bunch of results, gather links to said results, and then send them to the user to be displayed
This is where my understanding breaks. Why would displaying it as a summary mean the backend process is no longer a search engine?
The LLM is going over the search results, taking them as a prompt and then generating a summary of the results as an output.
The search results are generated by the good old search engine, the “AI summary” option at the top is just doing the reading for you.
And of course if the answer isn’t trivial, very likely generating an inaccurate or incorrect output from the inputs.
But none of that changes how the underlying search engine works. It’s just doing additional work on the same results the same search engine generates.
EDIT: Just to clarify, DDG also has a “chat” service that, as far as I can tell, is just an UI overlay over whatever model you select. That just works the same way as all the AI chatbots you can use online or host locally and I presume it’s not what we’re talking about.
I see, you’re splitting the UI from the backend as two different things, and Im seeing them as parts to a whole.