Products · Product
LangChain
Raised as a usability problem by 20 people on Hacker News over 2 years (2023–2024), in 16 threads.
No issue was raised by at least 3 people in 3 threads this year.
- 1
- 2
Every issue, all time, most people first
Verbose abstractions make the library hard to useUnreviewed
20232026- Design choices are very confusing, and the library is bloated2024-08-02
- Abstractions are overly verbose, making the library difficult to use2024-02-08
- Wrong abstraction makes the library more trouble than it's worth to use2023-11-01
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 21 complaints
- Interfaces are unintuitive, forcing constant digging through source code to learn usage2024-12-28
- Docs are hard to navigate and LangChain docs are hard to find2024-10-30
- Design choices are very confusing, and the library is bloated2024-08-02
- Documentation explains none of the methods, so users must read spaghetti source code to learn2024-06-21
- Confusing to tell which type fills which function in the chain2024-06-21
- Customizing anything in LangChain is extremely convoluted and hard to figure out2024-06-21
- Framework is over-bloated and confusing to work with2024-06-09
- API is inconsistent and verbose, obscuring what happens under the hood2024-04-03
- Abstractions are overly verbose, making the library difficult to use2024-02-08
- Hardcoded prompts make it difficult to experiment and iterate2023-11-28
- Wrong abstraction makes the library more trouble than it's worth to use2023-11-01
- Documentation is so poor that users must rely on other sources2023-07-18
- Basic list processing needs custom chains, prompts and agents to work2023-07-15
- Integrations barely work and sometimes stay broken for weeks2023-07-15
- Chat templates won't allow assigning proper user/assistant names, and components don't compose when used differently2023-07-09
- Documentation is hard to navigate and sometimes incomplete, and the library feels overly abstracted2023-06-01
- Too many wrappers, confusing what each one adds2023-05-19
- Debugging chain classes means stepping through a deep, tangled object hierarchy to learn what they do2023-05-05
- Documentation is confusing and omits explanations of key default parameters2023-05-05
- Hard to understand what chain classes do; debugging means endless nested calls2023-04-20
- Too many ways to do the same thing; hard to tell chat and completion LLMs apart2023-04-04