|
|
|
|
|
|
by hdjrudni
16 days ago
|
|
|
This looks pretty nice for humans too actually. The "for agents" is a bit of a turn off for me. Are they just trying to jump on the AI hype train or is this really AI-centric? Because if its for agents and only agents then I guess I should expect it to get progressively worse for humans but its for humans & agents then maybe it stays a nice clean human-friendly language. |
|
|
We have been building BAML for around 3 years -- originally it was a DSL for getting structured outputs from llms using what we call 'llm functions'
Our users told us they wanted to do more, so we made it an actual turing-complete language, still with a focus on people building AI workflows and calling nondeterministic models. This is why we added very flexible testing capabilities into BAML itself for test parameterization, dynamic tests, etc.
As we were building it, we realized humans weren't going to be the ones writing the code, so we started researching what we could do on this front. This led us to design BAML to use all fully-qualified-names for everything (classes, enums,functions etc) to name one example. We found in some cases AI agents saved 30% tokens navigating baml codebases vs TypeScript ones. There's no imports to track down, etc.
We do aim to keep humans in the loop, and we'll do some more deep dives that tackle each feature.