this post was submitted on 13 May 2025
459 points (100.0% liked)
TechTakes
1868 readers
147 users here now
Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.
This is not debate club. Unless it’s amusing debate.
For actually-good tech, you want our NotAwfulTech community
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
so what are the sentiments about langchain? I was recently working with it to try to build some automatic PR generation scripts but I didn't have the best experience understanding how to use the library. the documentation has been quite messy, repetitive and disorganized—somehow both verbose and missing key details. but it does the job I wanted it to, namely letting me use an LLM with tool calling and custom tools in a script
Given the volatility of the space I don't think it could have been doing stuff much better, doubt it's getting out of alpha before the bubble bursts and stuff settles down a bit, if at all.
Automatic pr generation sounds like something that would need a prompt and a ten-line script rather than langchain, but it also seems both questionable and unnecessary.
If someone wants to know an LLM's opinion on what the changes in a branch are meant to accomplish they should be encouraged to ask it themselves, no need to spam the repository.
seems like garbage to me
sounds like you figured out the referenced problem for yourself already
I've deployed LangChain to production shudders. My use case involved sending images results back to the "agent" and that use case is an after thought for many of these services. I ended up extending the Gemini Vertex client to fake it. The artifacts system is basically pass around a dictionary and pray both ends agree on the shape.
This is not an endorsement of LLMs in general. I'm working to replace it with a decision tree.