@UJADF897F btw, I checked:

borkdude@DESKTOP-JN2UNTV ~ $ /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe

Try the new cross-platform PowerShell 

PS Microsoft.PowerShell.Core\FileSystem::\\wsl$\Ubuntu-20.04\home\borkdude> clojure
Clojure 1.10.1
user=> (System/getProperty "os.arch")
"amd64"
;; Linux:
borkdude@DESKTOP-JN2UNTV ~ $ clojure
Clojure 1.10.1
user=> (System/getProperty "os.arch")
"amd64"
                                                                                                                                                                                                         ;; MacBook

$ clj
Clojure 1.10.1
user=> (System/getProperty "os.arch")
"x86_64"

so on macOS or maybe depending on which Java version you are on, os.arch responds with x86_64 or amd64 hmm

ah ok they are the same though right ? I just copied what had been auto generated in the binaries I created tbh

yeah, maybe the package manager should just deal with that

I'll fix that, thanks

It needs some more work around keeping track of the started jvm processes, but the basics work

why not directly go with Clojure in this case, would be the obvious question?

True, i’m thinking you could have a process running in the background that can deal with the things that Babashka can’t. So if you use AWS a lot it only needs to start once

yeah. can also use the nREPL client for that

yeah maybe that would be an alternative. This is using the prepl so same idea i guess

cool idea

it’s a combination of pods and this idea https://github.com/jeroenvandijk/clojure-scripting

:thumbsup:

Writing a pod in babashka itself was easier than i had expected

Have you already tested the tzzh aws pod, since you are interested in AWS stuff?

You can now install it using glam :)

No I haven’t. My main concern is not having to learn new libraries 😅 I think the tzzh aws pod is inventing a new API

i’ll check it out now before i say something stupid

I think a similar approach could work for Clojure. Just generate all the code at compile time instead of using reflection/dynamic requires

(at least, that's how I think the cognitect lib works?)

yeah I agree. pretty sure the aws-api can be made compatible with Graalvm

it just requires some work

the tzzh pod looks quite easy to use though.

although I don't know the Java AWS API, I can't imagine why they would re-invent a different API in Go or Python

it's all going to the same endpoints eventually I guess

no i mean the clojure api is not the same

the backend is definitely the same

so I mean the api of pod-tzzh-aws is not the same as cognitect aws-api. So i would have to learn both

cannot reuse my code

And personally I don’t want to debug go code if things go wrong

But that’s just me. it’s nice that pod-tzz-aws exists

fair

I think the idea to use a small fast starting script to invoke something in a larger stateful context is similar to Datomic Ions with AWS Lambda + Datomic running on other machines

so you could have one Clojure REPL running on an EC2 instance permanently

and babashka in AWS lambda sending commands to its REPL

yeah i think you are right, pretty similar

It could also be useful if stateful means loading a really big library that would otherwise impact startup time

I’m not sure if the prepl should be used for concurrent commands, but the concept could be implemented via other protocols as well

nREPL supports this well via ids

sounds like its more suited for something like this then

Small example: https://github.com/borkdude/babashka#communicating-with-an-nrepl-server

A more full example can be seen in the tests of babashka.nrepl

The babashka pod protocol is more or less the same as nREPL, with a few twists

cool, i haven’t really dived into that protocol yet. Not sure what the tradeoffs are compared with the prepl protocol

is this a way to generically use any clojure/java library?

(I am looking for a quick way to run the Mongo or the RabbitMQ clients in babashka 😄)

Oh I see what you did there, kinda cool good job!

Yeah the idea is that anything that tools.deps can load, can be accessed via this pod

Currently there is no proper management of the backend process and the port is hardcoded right now, but this can be fixed

And maybe some error scenarios are hard to debug because of the limited communication between the pod and the babashka process right now. Probably needs another layer to get this right

seems like this could be a good candidate for being embedded in babashka.. pods are nice for interop with other langs but if you already have a clojure libs it can be easier

Yeah maybe. Pods give us a nice way to experiment with this idea for now at least. If you want to try with Mongo and RabbitMQ I can help out if you run into problems

doesn't mongo support an http api btw?

I think it does

actually no, https://stackoverflow.com/questions/7386740/does-mongodb-have-a-native-rest-interface

you are too quick 🙂 I can only add clojure.string/split-lines over str/split

ah, good one

I like to let bb to the input, so I would prefer this:

cat file.txt | bb -i '(-> *input* sort distinct)'

seems a bit cleaner

I think he needs frequencies , no?

yep, that uniq -c is the tricky peace

ah, true, replace distinct with frequencies

cat file.txt | bb -i -O '(-> *input* sort frequencies)'

to make the number show up first:

cat file.txt | bb -i -O '(-> *input* sort frequencies (->> (map reverse)))'

absolute closest to the original:

cat file.txt | bb -i -o '(-> *input* sort frequencies (->> (map reverse) (map (partial str/join " "))))'

ok, I'll stop now, bb is just too fun

Nicer formatting:

cat README.md | bb -io '(->> *input* sort frequencies (map (fn [[l n]] (format "%3s %s" n l))))'

thank you! i've added couple of things and end up with

tshark -r /var/tmp/DNS.pcap00.gz -T fields -e dns.qry.name dns.qry.type==1 | bb -io '(->> *input* sort frequencies clojure.set/map-invert (into (sorted-map)) (map (fn [[k v]] (format "%6s %s" k v))))'

:thumbsup: clojure power!

wow

be careful with map-invert, it'll collapse ties

(clojure.set/map-invert {:foo 1 :bar 1}) -> {1 :bar}

I tried this, but I still get the same error

hmm, shucks. that fixed postal for me in a normal JVM context. not sure what more graal will need 😕

I fixed that by adding a class to the reflection config. Now I'm looking at `javax.activation.UnsupportedDataTypeException: no object DCH for MIME type text/plain; charset=utf-8 `

feels like we're going down the rabbit hole of javax.mail soon. (i WORK at a clojure shop that deal with email, so a rabbit hole it is)

Summary in https://github.com/borkdude/babashka/issues/599

Maybe writing it as a pod wrapping that other library could work