I went through this page:
https://boundaryml.com/explore
But I'm afraid it didnt quite click with me. I mostly asked the question cause a couple of my friends recently bought up the topic of BAML and i wanted to see stuff for myself.
Here's some feedback (I'm keeping it blunt in the spirit of transparency)
My perfective going in: "Cool, a language for agents... so how does this help me build agentic systems better?"
1. Part 1 is mostly about its features as a programming language. Out of experience i know thats awesome... but none of those are problems for me today. Typescript with the effect library gives me a "good-enough" layer.
2. Part 2 is where things start getting interesting. 1st and 2nd point are good to know. But 3 onwards is what excites me. It shows that baml can be treated almost as an interpreted language now. And given my past experience knowing how baml functions work i know how awesome this can be.
3. The workflow explorer is what really got my attention. Cause it reminded me the kind of low level control baml could potentially have on llm responses. The whole workflow conversation that i had with Vaibhav on my stream.
4. Part 5 was the most important piece (the thing i actually was trying to find since baml is supposed to be a language for agents after all). But it doesn't go into any details I wanted to see. I was really hoping to get some insights on how this helps me conpared to the other tools i am evaluating (like PI, claude agent sdk, even flue framework).