Yeah agree. I spent a few hours looking at the langchain repo when it first hit the scene and could not for the life of me understand what value it actually provided. It (at least at the time) was just a series of wrappers and a few poorly thought through data structures. I could find almost no actual business logic.

My first surprise on it:

I made an error trying with aws bedrock where I used "bedrock" instead of "bedrock-runtime".

The native library will give you an error back.

Langchain didn't try and do anything, just kept parsing the json and gave me a KeyError.

I was able to get a small fix, but was surprised they have no error like ConfigurationError that goes across all their backends at all.

The best I could get them to add was ValueError and worked with the devs to make the text somewhat useful.

But was pretty surprised, I'd expect a badly configured endpoint to be the kind of thing that happens when setting stuff up for the first time, relatively often.

Isn't that what a lot of this is about? It's a blue ocean and everyone are full of fomo.