<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Llamaindex - Tag - vo.rs</title><link>https://vo.rs/tags/llamaindex/</link><description>Llamaindex - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 30 Apr 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/llamaindex/" rel="self" type="application/rss+xml"/><item><title>LangChain vs LlamaIndex: Orchestrating LLMs Without Going Mad</title><link>https://vo.rs/story/langchain-vs-llamaindex-orchestrating-llms-without-going-mad/</link><description>&lt;p&gt;The moment you try to build anything real with a language model, you discover the hard part isn&amp;rsquo;t the model. It&amp;rsquo;s everything around it: loading documents, splitting them sensibly, embedding them, stuffing the right context into a prompt, calling a tool, parsing the reply, and doing it all again. You can write this yourself — I did, twice, badly — or you can reach for a framework. The two that dominate are &lt;strong&gt;LangChain&lt;/strong&gt; and &lt;strong&gt;LlamaIndex&lt;/strong&gt;, and the internet will cheerfully tell you to use both, neither, or that one is bloated and the other is a toy. Here&amp;rsquo;s what I actually think after building with each.&lt;/p&gt;</description><pubDate>Tue, 30 Apr 2024 09:00:00 +0000</pubDate></item></channel></rss>