Clojurians Log v2

@cap10morgan about the bb.edn pods, in this video Daniel Amber uses uberscript in combination with pods: https://youtu.be/jm0RXmyjRJ8 It might be good to support that too, e.g. just prepend load-pods into the uberscript or so, derived from bb.edn pods

I'm ok with doing that in a second PR or so, but might be good to have on our radar

Or maybe we can support babashka.pods/declare or so, a programmatic equivalent to the declarative one and re-use the code as much as possible

@borkdude For pods that need to communicate over a socket, do we need to add that to the bb.edn pod declaration? Something like {:pods {my.socket/pod {:version "0.1.0" :transport :socket}}}? Or is it expected that these can do a :describe over stdio?

No, this this should be part of the manifest

See e.g. spire

https://github.com/babashka/pod-registry/blob/76f612df70e54041a812bb2a4e994c6654eb475f/manifests/epiccastle/spire/0.1.0-alpha.17/manifest.edn#L5

The idea is that the user shouldn't have to know this