Strands is more opinionated and higher-level, also not vendor neutral.

So decorators here specifically attach metadata to make a function a reusable component. Builder makes a workflow. In Hamilton it's all decorators because it's purely declarative construction (sans reusability, really).

Right it was a bit of a joke. Originally stefan and I presented frameworks when we were at stitch fix -- stefan called his "hamilton" and I called mine "burr". His was better for the use-case. But then we wanted to build something for state machines as opposed to DAGs, so we called it Burr. I wanted the git tagline to be "make your agents go burr..."

Ha! We went all out on the modern one (user contribution!).

This is where it's nice to have some guardrails -- coding agents work etremely well with limitations.

Right I think this is why we made it unopinioated to a fault. Burr doesn't really do these things rather it just provides an orchestration framework. So it's pure BYO functions, classes, components, etc...

Right -- possible it's slightly out of date https://github.com/apache/burr#-comparison-against-common-fr.... Good point on differentiating.

One of the co-creators/maintainers here! Will try to answer Qs over the day.

Do you ever abbreviate the project name as A. Burr and how many Hamilton jokes[1] result from this?

[1] https://en.wikipedia.org/wiki/Burr%E2%80%93Hamilton_duel

wait till you see our other project github.com/apache/hamilton ;)

How does it compare to the Strands Agents SDK? https://strandsagents.com

And then says... "you're welcome"

Ok do this but for JavaScript