- learning the framework is a one-time cost that pays dividends over multiple projects. Subsequent products can be built by only implementing the domain-specific stuff above the framework.
- presumably the stuff solved by the framework is non-trivial. It might be “obvious” (in hindsight) but chances are the framework designer has thought about it much more than we want to.
- (theoretical) the framework will outlive any single generation of LLM. This is a fast-moving space and learning a new API or model every few months isn’t going to be fun. Hopefully the framework will adapt and adopters can transition to new models using one framework they already know.
Only the third really applies to an existing project adopting the framework. Is that applicable in your case?