4 ms·
It was the first pass at solving the common problems when building with LLMs. People jumped on it because it was trendy and popular. But it quickly became obvi
by chatmasta 2y ago
It was the first pass at solving the common problems when building with LLMs. People jumped on it because it was trendy and popular.
But it quickly became obvious that LangChain would be better named LangSpaghetti.
That’s nothing against the authors. What are the chances the first attempt at solving a problem is successful? They should be commended for shipping quickly and raising money on top of it to keep iterating.
The mistake of LangChain is that they doubled down on the bad abstraction. They should have been iterating by exploring different approaches to solving the problem, not by adding even more complexity to their first attempt.
- dongobread 2y agoLangchain feels very much like shovelware that was created for the sole purpose of parting VCs of their money. At one point the codebase had a "prompt template" class that literally just called Python's f-string.
- hdhshdhshdjd 2y ago[dead]
- jhoechtl 2y agoDoesn't langchain provide useful functionality when it comes to RAG? Here it seems it does considerably more but being a mere shim abstraction?
- seanhunter 2y agoNot really. It's pretty much the same for RAG as it is for everything else - just a thin additional abstraction on top of apis that are easy to call on their own.
- __loam 2y agoGood thing they didn't raise money to develop this piece of crap. https://blog.langchain.dev/announcing-our-10m-seed-round-led-by-benchmark/ https://blog.langchain.dev/announcing-our-10m-seed-round-led...