Father, Software Engineer, ML and data type. Long COVID since Dec 2021.
- Tweets2K
- Following233
- Followers475
- Likes163
ALT A few bullet points: - LangChain encourages tool lock-in for little developer benefit, as noted in the OP. There is no inherent advantage into using them, and some have suboptimal implementations. - The current implementations of the ReAct workflow and prompt engineering are based on InstructGPT (text-davinci-003), and are extremely out of date compared to what you can do with ChatGPT/GPT-4. - Debugging a LangChain error is near impossible, even with verbose=True. - If you need anything outside the workflows in the documentation, it's extremely difficult to hack, even with Custom Agents. - The documentation is missing a lot of relevant detail (e.g. the difference between Agent types) that you have to go diving into the codebase for. - The extreme popularity of LangChain is warping the entire AI ecosystem around the workflows to the point of harming it. Recent releases by Hugging Face and OpenAI recontextualize themselves around LangChain's "it's just magic AI" to the point of hurting
![digitcatphd on July 9, 2023 | root | parent | next [–] | Josh Devins](https://pbs.twimg.com/card_img/2117555880887472128/u5fnNnhB?format=png&name=800x419)
ALT a flyer for a read-in demonstration being held at Brandenburg Gate in Berlin, Germany, on May 10, 2023, from 2 p.m. to 4 p.m.
ALT Me lying in bed, with Dr. Kitty on call.
