5 ms·

People still use langchain?

by dcreater 1y ago

zingababba 1y ago
What should be used instead?
- Hugsun 1y ago
  I gave up after it didn't let me see the prompt that went into the LLM, without using their proprietary service. I'd recommend just using the API directly. They're very simple. There might be some simpler wrapper library if you want all the providers and can't be bothered to implement the support for each. Vercel's ai-sdk seems decent for JS.
  - halyconWays 1y ago
    >I gave up after it didn't let me see the prompt that went into the LLM, without using their proprietary service. Haha, really?
- ebonnafoux 1y ago
  httpx to make the call yourself, or if you really want a wrapper the openAI python https://github.com/openai/openai-python https://github.com/openai/openai-python.
- Jimmc414 1y ago
  pydanticai, dspy or deal directly with the provider sdks
  - dcreater 1y ago
    DSPy seems like the right, developed approach but its far too convoluted and I find the grammar is ugly.
- dcreater 1y ago
  Plain old http requests and your own functions. Its almost always the better choice
owebmaster 1y ago
No
deleted 1y ago
[deleted]
anshumankmr 1y ago
Its good for quickly developing something but for production, I do not think so.We used it for a RAG application I built last year with a client, ended up removing it piece by piece, and found our app responded faster. But orgs think its some sort of flagbearer of LLMs.As I am interviewing for other roles now, HRs from other companies still ask for how many years of exp I have with Langchain and Agentic AI.
codestank 1y ago
i do because i don't know any better since i'm new to the AI space.
- nilamo 1y ago
  My experience, as someone who is also new and trying to figure things out, is that langchain works great as long as everything you want to do has an adapter. Try to step off the path, and things get really complex really fast. After hitting that several times, I've found it's easier to just do things directly instead of trying to figure out the langchain way of doing things. I've found dspy to work closer to how I think, which has made working with pipelines so much easier for me.
screye 1y ago
It is useful if you keep swapping things out. Langchain's wrappers stay stable and up-to-date because of their popularity. In production, it's ideal startups that undergo a lot of flux. I would suggest against using their orchestration tooling, DSLs or default prompts. Those components are either underbaked or require deep adoption in a way that is harder to strip out later. We change models, providers and search tooling quite often. Having consistent interfaces helps speed things up and reduce legacy buildup. Their stream callbacks, function calling integration, RAG primitives and logging solutions are nice. One way of another, it is useful to have a langchain-like solution for these needs. Pydanticai + logfire seems like a better version of what I like about langchain. Haven't tried it, but I bet it's good.

People still use langchain?

zingababba 1y ago

What should be used instead?

Hugsun 1y ago
I gave up after it didn't let me see the prompt that went into the LLM, without using their proprietary service. I'd recommend just using the API directly. They're very simple. There might be some simpler wrapper library if you want all the providers and can't be bothered to implement the support for each. Vercel's ai-sdk seems decent for JS.
- halyconWays 1y ago
  >I gave up after it didn't let me see the prompt that went into the LLM, without using their proprietary service. Haha, really?
ebonnafoux 1y ago
httpx to make the call yourself, or if you really want a wrapper the openAI python https://github.com/openai/openai-python https://github.com/openai/openai-python.
Jimmc414 1y ago
pydanticai, dspy or deal directly with the provider sdks
- dcreater 1y ago
  DSPy seems like the right, developed approach but its far too convoluted and I find the grammar is ugly.
dcreater 1y ago
Plain old http requests and your own functions. Its almost always the better choice

owebmaster 1y ago

deleted 1y ago

[deleted]

anshumankmr 1y ago

Its good for quickly developing something but for production, I do not think so.We used it for a RAG application I built last year with a client, ended up removing it piece by piece, and found our app responded faster. But orgs think its some sort of flagbearer of LLMs.As I am interviewing for other roles now, HRs from other companies still ask for how many years of exp I have with Langchain and Agentic AI.

codestank 1y ago

i do because i don't know any better since i'm new to the AI space.

nilamo 1y ago
My experience, as someone who is also new and trying to figure things out, is that langchain works great as long as everything you want to do has an adapter. Try to step off the path, and things get really complex really fast. After hitting that several times, I've found it's easier to just do things directly instead of trying to figure out the langchain way of doing things. I've found dspy to work closer to how I think, which has made working with pipelines so much easier for me.

screye 1y ago

It is useful if you keep swapping things out. Langchain's wrappers stay stable and up-to-date because of their popularity. In production, it's ideal startups that undergo a lot of flux. I would suggest against using their orchestration tooling, DSLs or default prompts. Those components are either underbaked or require deep adoption in a way that is harder to strip out later. We change models, providers and search tooling quite often. Having consistent interfaces helps speed things up and reduce legacy buildup. Their stream callbacks, function calling integration, RAG primitives and logging solutions are nice. One way of another, it is useful to have a langchain-like solution for these needs. Pydanticai + logfire seems like a better version of what I like about langchain. Haven't tried it, but I bet it's good.