> Using someone else's abstractions for your entire workflow is a nice way of making a hackathon project
We use someone else's abstractions all the time, when they are good :) Think of reactjs, expressjs, django, etc.
> Abstracting away the flows (agency/langchain) is the wrong layer of abstraction
But you do abstract away SQL when you write business logic isn't it? Many people uses ORMs for that, which gives ability to easily switch databases and write tests. Why do you think this isn't the same?
> langchain had hardcoded prompts, which make it difficult to experiment and iterate
Agency does not and won't have anything like that except it's going to make a LOT of sense. Even then there 100% will be to control that stuff.
> Where is the complexity hidden?
The biggest complexity was to design the library to be small, simple and extensible. It's not a lot of abstractions out there.
But the better answer to your question is probably something like - "complexity is hidden behind how providers implement core interfaces"
We use someone else's abstractions all the time, when they are good :) Think of reactjs, expressjs, django, etc.
> Abstracting away the flows (agency/langchain) is the wrong layer of abstraction
But you do abstract away SQL when you write business logic isn't it? Many people uses ORMs for that, which gives ability to easily switch databases and write tests. Why do you think this isn't the same?
> langchain had hardcoded prompts, which make it difficult to experiment and iterate
Agency does not and won't have anything like that except it's going to make a LOT of sense. Even then there 100% will be to control that stuff.
> Where is the complexity hidden?
The biggest complexity was to design the library to be small, simple and extensible. It's not a lot of abstractions out there.
But the better answer to your question is probably something like - "complexity is hidden behind how providers implement core interfaces"