It's not as ergonomic as they made it to be.

The fact that you have to bundle input+output signatures and everything is dynamically typed (sometimes into the args) just make it annoying to use in codebases that have type annotations everywhere.

Plus their out of the box agent loop has been a joke for the longest time, and writing your own if feasible but it's night and day when trying to get something done with pydantic-ai.

Too bad because it has a lot of nice things, I wish it were more popular.

▲

sbpayne 6 hours ago | parent [-]

Yeah! I can agree with this. There's some improved ergonomics to get here

▲

verdverm 6 hours ago | parent [-]

Have you looked at ADK? How does it compare? Does it even fit in the same place as Dspy?

https://google.github.io/adk-docs/

Disclaimer, I use ADK, haven't really looked at Dspy (though I have prior heard of it). ADK certainly addresses all of the points you have in the post.

▲

sbpayne 5 hours ago | parent [-]

I personally haven't looked super closely at ADK. But I would love if someone more knowledgeable could do a sort of comparison. I imagine there are a lot of similar/shared ideas!

	▲	verdverm 5 hours ago \| parent [-]
		There are dozens if not 100s of agent frameworks in use today, 1000s if you peruse /new. I'm curious what features will make for longevity. One thing about ADK is that it comes in four languages (Py, TS, Go, Java; so far), which means understanding can transfer over/between teams in larger orgs, and they can share the same backing services (like the db to persist sessions).