Ask HN: What are the LangChain's parts not easy replicable with custom code?

For individuals who have invested significant time in developing LLM-based applications using Langchain, it's important to acknowledge that a critical perspective on Langchain has been expressed in various articles and discussions. Given this context, I would like to inquire about the specific aspects of Langchain that, in your experience, stand out as being challenging to replicate with custom code. In other words, considering the potential criticisms and recognizing your expertise, could you elaborate on the strengths and unique functionalities of Langchain that make it a valuable choice in LLM integration and that are not easily replaceable through the development of custom solutions? Your insights will be valuable in shedding light on Langchain's merits and differentiators for the benefit of others in the field.

Here are some problems identified by the users, but I would like to find the gems in LangChain that justify using it.

Problems:

1. Overly complex and unnecessary abstractions 2. Easy breakable and unreliable 3. Poor documentation 4. A high level of abstraction hinders customization 5. Inefficient token usage 6. Difficult integration with existing tools 7. Limited value proposition 8. Inconsistent behavior and hidden details 9. Better alternatives available 10. Primarily optimized for demos