From a discussion with a friend today.. Are embeddings a hack? Is building out tooling and databases and APIs and companies around embeddings all going to be for naught as soon as there's a solid LLM/API with a big enough context window?
Creating AI assistant with GPT and Ruby and Redis using embeddings
21–26 of 26 posts
Re: Creating AI assistant with GPT and Ruby and Redis using embeddings
#22Re: Creating AI assistant with GPT and Ruby and Redis using embeddings
#23Re: Creating AI assistant with GPT and Ruby and Redis using embeddings
#24From a discussion with a friend today.. Are embeddings a hack? Is building out tooling and databases and APIs and companies around embeddings all going to be for naught as soon as there's a solid LLM/API with a big enough context window?
The short answer is that, yes, embeddings are probably a hack in the same way that using bits or short variable names were hacks to reduce memory usage. At some point you are correct: someone would prompt "given , answer ".
Yes - embeddings are a hack:
No - there won't anything like a "real API" unless there's a new discovery or a shift in the way LLMs are constructed. It's not theoretically impossible but there's no clear way to get guaranteed results from present day LLMs, all they do output guesses from their input text (combining prompt text and then user text).
Re: Creating AI assistant with GPT and Ruby and Redis using embeddings
#25From a discussion with a friend today.. Are embeddings a hack? Is building out tooling and databases and APIs and companies around embeddings all going to be for naught as soon as there's a solid LLM/API with a big enough context window?
Re: Creating AI assistant with GPT and Ruby and Redis using embeddings
#26Earlier quoted context omitted.
Even with an incredibly long context window (say, 1M tokens), attention still suffers from a problem with long-term dependencies. This is probably why OpenAI hasn't publicly released their 32k token length model just yet.
I think they haven't released it because the capabilities it has are simply too powerful when combined with a vectorDB.