Comment by albert_e | Hacker News Reader

Comment by albert_e | Hacker News Reader

Parent Full thread

Can you elaborate a little on why LangChain is bad and should be avoided?

I had modest success in using LLMs to achieve productivity improvements and results for my clients that are otherwise not possible. I used more direct API calls to invoke LLMs so far but am now considering switching to LangChain to make it more maintainable and scalble to turn more of my ideas into products and service offerings for my clients.

At the outset, a standard library that warps around popular LLMs and makes calling them easier seems needed and inevitable.

Low quality code and a lot of technical debt.

Okay -- I havent come across a critique of LangChain yet. Just starting to learn and use it.

I suppose if LangChain doesnt find a good path to becoming more mature -- then some other equivalent open-source library will replace it in coming months.

Thanks for the heads-up.

Can you substantiate this claim?

```

def embed_documents(self, texts: List[str]) -> List[List[float]]:

    texts = list(map(lambda x: x.replace("\n", " "), texts))
    embeddings = self.client.encode(texts, \*self.encode_kwargs)
    return embeddings.tolist()

```

lol when has this ever been an issue other than philosopher programmers

LangChain will not make the project any more maintainable than you can on your own. Avoid it.

Reply on news.ycombinator.com