Clojurians Log v2

@dainius.jocas Could it be that the slowness with curl was with repeated execution of requests? Maybe clj-http-lite uses connection pooling?

I doubt that the slowness is because connection pooling. As it is written in the README No persistent connection support

I have a suspicion that it might be because doing shell out on a very constrained environment, just 128MB RAM and very little CPU. I would like to test with more RAM given to the lambda and some profiling.

I have an idea to package babashka as a Lambda layer, and make a proper template that uses handler option, that would be a script file. In this way one could write a lambda function right in the cloud IDE or the packaging script could produce --uberscript for compactness. @borkdude what do you think if I publish babashka as a public lambda layer?

:thumbsup:

@dainius.jocas Btw, if you want to develop babashka.curl you can load it with bb from the classpath with :reload, instead of the built-in one.