Hearing this perspective helps put my frustration in context. I need to lower my expectations and just get used to its quirks. Despite its issues I've had a ton of fun building with langchain and will keep using it.
The Problem with LangChain
21–30 of 97 posts
Re: The Problem with LangChain
#22I generally agree, but why so polemic? I mean, it starts by giving the full name of the original author… calls using his free software a waste of time… destroys the design as if tearing down someone’s work who made bad decisions at every turn when making a brand-new thing that is FOSS. Did anyone else find that a bit strange? Did I miss the light-hearted tone buried somewhere? That said, strangely… useful examples an…
Anyone who's been burned by LangChain, especially now that it has VC funding, has to be worried that LangChain will become the cross-LLM standard library™, and they'll be dealing with it and endless patches to it for the rest of their lives. (Think systemd or NPM or Python packaging.) If it's as bad as described, the time to stop LangChain is to strangle it in the cradle, before it can get too far or risks finding a killer-app/niche which will immortalize it no matter how bad it is.
Re: The Problem with LangChain
#23I generally agree, but why so polemic? I mean, it starts by giving the full name of the original author… calls using his free software a waste of time… destroys the design as if tearing down someone’s work who made bad decisions at every turn when making a brand-new thing that is FOSS. Did anyone else find that a bit strange? Did I miss the light-hearted tone buried somewhere? That said, strangely… useful examples an…
https://gwern.net/holy-war Anyone who's been burned by LangChain, especially now that it has VC funding, has to be worried that LangChain will become the cross-LLM standard library™, and they'll be dealing with it and endless patches to it for the rest of their lives. (Think systemd or NPM or Python packaging.) If it's as bad as described, the time to stop LangChain is to strangle it in the cradle, before it can get…
Re: The Problem with LangChain
#24Disclaimer: I am the author of txtai
Re: The Problem with LangChain
#25If you'd like another LLM framework option that also is a vector database, check out txtai ( https://github.com/neuml/txtai ). Disclaimer: I am the author of txtai
Re: The Problem with LangChain
#26As long as you're cycling data between LLM unstructured text is going to be just fine.
Have your tools accept natural language as well, and you're golden.
Re: The Problem with LangChain
#27I generally agree, but why so polemic? I mean, it starts by giving the full name of the original author… calls using his free software a waste of time… destroys the design as if tearing down someone’s work who made bad decisions at every turn when making a brand-new thing that is FOSS. Did anyone else find that a bit strange? Did I miss the light-hearted tone buried somewhere? That said, strangely… useful examples an…
I think you're reading into the tone too much, but I address this very argument at the end. > No one wants to be that asshole who criticizes free and open source software operating in good faith like LangChain, but I’ll take the burden. To be clear, I have nothing against Harrison Chase or the other maintainers of LangChain (who encourage feedback!). However, LangChain’s popularity has warped the AI startup ecosystem…
"simpleaichat is a Python package for easily interfacing with chat apps like ChatGPT and GPT-4 with robust features and minimal code complexity. This tool has many features optimized for working with ChatGPT as fast and as cheap as possible, but still much more capable of modern AI tricks than most implementations"
https://github.com/minimaxir/simpleaichat
Separately, in the article, typo expect->except here:
"LangChain uses about the same amount of code as just using the official openai library, expect LangChain incorporates more object classes for not much obvious code benefit."
Re: The Problem with LangChain
#28Re: The Problem with LangChain
#29It’s still very early days for software composing AI models and we almost certainly don’t have all the right metaphors yet. And I think there is a lot to be said for strong typing and simple, robust code!
Re: The Problem with LangChain
#30I generally agree, but why so polemic? I mean, it starts by giving the full name of the original author… calls using his free software a waste of time… destroys the design as if tearing down someone’s work who made bad decisions at every turn when making a brand-new thing that is FOSS. Did anyone else find that a bit strange? Did I miss the light-hearted tone buried somewhere? That said, strangely… useful examples an…
https://gwern.net/holy-war Anyone who's been burned by LangChain, especially now that it has VC funding, has to be worried that LangChain will become the cross-LLM standard library™, and they'll be dealing with it and endless patches to it for the rest of their lives. (Think systemd or NPM or Python packaging.) If it's as bad as described, the time to stop LangChain is to strangle it in the cradle, before it can get…