|
|
|
|
|
by jonathan-adly
556 days ago
|
|
I would strongly advise against people learning based on LangChain. It is abstraction hell, and will set you back thousands of engineers hours the moment you want to do something differently. RAG is actually very simple thing to do; just too much VC money in the space & complexity merchants. Best way to learn is outside of notebooks (the hard parts of RAG is all around the actual product), and use as little frameworks as possible. My preferred stack is a FastAPI/numpy/redis. Simple as pie. You can swap redis for pgVector/Postgres when ready for the next complexity step. |
|
My experience with LangChain has been a mixed bag. On the one hand it has been very easy to get up and running quickly. Following their examples actually works!
Trying to go beyond the examples to mix and match concepts was a real challenge because of the abstractions. As with any young framework in a fast moving field the concepts and abstractions seem to be changing quickly, thus examples within the documentation show multiple ways to do something but it isn't clear which is the "right" way.