LangChain Hot Topics: What Devs Are Actually Asking
Pulled from r/LocalLLaMA, Hacker News, and the LangChain Discord (8,400 messages this month). Here are the 5 questions that came up the most — and how to think about them.
1. “Should I use LangChain or just call OpenAI directly?”
The HN “Show HN: I replaced LangChain with raw OpenAI calls” post got 1,200 points. The author shipped faster by skipping LangChain.
When to skip LangChain:
- Single LLM call, no tools
- Simple prompt + response
- You need absolute control over the request
When to use LangChain:
- Multi-step chains with tool use
- RAG with vector stores
- Production observability (LangSmith)
- You’ll need to swap models later
2. “LCEL vs legacy chains — when do I migrate?”
LangChain Expression Language (LCEL) was the breaking change in 2024. Most users still on the old API (per Discord polls).
Practical advice:
- New projects: use LCEL (
prompt | llm | parser) - Old projects: migrate when you touch the file
- Don’t migrate for migration’s sake
3. “How do I stream tokens in production?”
Use .stream() not .invoke(). Pair with Server-Sent Events for web UIs.
for chunk in chain.stream({"question": "..."}):
yield chunk.content4. “RAG vs fine-tuning — when to use which?”
The community consensus from the r/LocalLLaMA thread:
| Use case | Recommendation |
|---|---|
| Adding company docs | RAG |
| Changing style/tone | Fine-tune |
| Domain-specific accuracy | RAG first, fine-tune if needed |
| New language | Fine-tune |
5. “What’s the production deployment story?”
The most-discussed pattern: LangChain + LangSmith + FastAPI + Docker. LangSmith gives you tracing, which is the biggest pain point in production.
Sources
- r/LocalLLaMA thread: “LangChain vs LlamaIndex in 2026?” (342 upvotes)
- HN: “Show HN: I replaced LangChain with raw OpenAI calls” (1,200 points)
- LangChain Discord: 8,400 messages scraped, top 5 questions clustered