Ah, we're doing tool calling to ourselves. Neat though!

Tell me more about the server side tools? I'm currently using dartantic in this fashion!

It was a fun day though!

A culture of violent, dehumanizing rhetoric is already rotting the world, fueled by click-bait greed and tribal politics.

Barf. You can have fancy sidewalks and a decent roadway. My 'hood has power poles that cut off the usable sidewalk and it's aggravating as hell, but at least we have something to walk on.

Sorry, *anti-sidewalk*?!

I'll try to land this first and then experiment with jaspr

Don't thank me yet - I need to land this internally and that might take a smidge of work.

You want the grpc protos for your service to automatically build some REST routes on say "shelf"?

protofu is fast because it doesn't use anything else and self-compiles the first time its run. I know there is some rough edges around maybe updating the version number(?) but I've not investigated.

IF (and I'm talking speculatively) you were to have this; what would you expect the folder structure to be?

I'm thinking everything goes in pubspec.yaml, use workspaces, and maybe have an extra line for build: some script (in case you want to use your friendly neighborhood protofu lib)

Yeah, engineers are not known to naming things well. Doing buildpacks with gcp first is far easier at the moment. If you look here, you'll see its a different beast:

github.com/GoogleCloudP...

This is my GCP cooking. Having to learn buildpacks, go, bazelisk, getting it to run on a M3 mac, _and_ keep my dayjob.

IAMAPM. To be clear, there is no official plans, designs, or anything else.

I'm cooking in the buildpacks for GCP because I'm stubborn and have been known to run Flutter and Dart in interesting places (google fiber set top boxes, TVs with teeny-tiny micro browsers).