Look no further than setup-clojure and use bb: latest https://github.com/DeLaGuardo/setup-clojure

Doh! We already use that 😄

It also uses clj-kondo, ahhh I can drop that from our deps.edn

Just:

bash < <(curl -s )

I think a quick reference in the docs would go a long way for others too (if you endorse the above-linked setup-clojure) 🙂

I'd second the install script based method too, keeps my stuff ci agnostic 😄 and pretty quick too

the install script is mentioned in the README of babashka

github actions are more declarative and support caching too

yep, but more often than not im not using actions, reasons like bigger machines etc 😅

@U04V15CAJ sure, the install script is the least common denominator. Interestingly, when I google "github action babashka" I see: • https://github.com/marketplace/actions/babashka-clojure • https://github.com/marketplace/actions/setup-babashka-a-clojure-babushka-for-the-grey-areas-of-bash • https://github.com/babashka/babashka/actions So I was more thinking a section in the readme just mentioning github actions (even if it is already just repeating the install script, if you don't want to mention specific github actions).

Sure, I'll add it

Added: https://github.com/babashka/babashka#ci

Thank you!

cc @U06F82LES

jonathandavenport@Jonathans-MacBook-Air ~ % asdf install babashka latest
* Downloading babashka release 1.0.169...
/Users/jonathandavenport/.asdf/plugins/babashka/bin/../lib/utils.bash: line 52: arch: unbound variable
rm: /Users/jonathandavenport/.asdf/installs/babashka/1.0.169/babashka-1.0.169.: No such file or directory
asdf-babashka: Expected /Users/jonathandavenport/.asdf/installs/babashka/1.0.169/bin/bb to be executable.
asdf-babashka: An error ocurred while installing babashka 1.0.169.
jonathandavenport@Jonathans-MacBook-Air ~ %

Just tried this on my M1

also hadn't heard of asdf before so thanks 🙂

This seems a bit broken then ...

% file $(asdf which bb)
/Users/user/.asdf/installs/babashka/1.0.165/bin/bb: Mach-O 64-bit executable arm64

Compare

% file $(which bb)
/Users/user/.asdf/shims/bb: Bourne-Again shell script text executable, ASCII text

asdf installs bash shims for all its binaries

@U04GSQQ6TAR this works for me - not sure what's going on on your machine

Does this work for you asdf install nodejs latest?

yes nodejs installs

@U04V15CAJ I've seen problems in our team, maybe, with machines getting binaries for the wrong platform after updating to a new version of osx

@U04GSQQ6TAR looks like this is tracked here https://github.com/fredZen/asdf-babashka/issues/3

case "$(uname -m)" in
    aarch64) arch=aarch64 ;;
    x86*) arch=amd64 ;;
  esac

when I run uname -m I get arm64

https://github.com/fredZen/asdf-babashka/pull/7

I have no idea, however, why this is working for me

I'm on macOS 12.6.1

I'm on 11.2.2

that might be the relevant difference

maybe relevant? https://github.com/Homebrew/homebrew-core/issues/71782

can you try which uname?

I get /usr/bin/uname

yep I get the same result

Yep, that PR should work

fwiw I also get arm64

The babashka install script also checks arm64 on macos

This is why I was suspicious that it wouldn't work on asdf, since I saw they weren't doing this

if that author is unresponsive, we could fork the repo

FWIW I've asked around in my team and most people seem to be properly getting the arm64 binary

I wonder how that is possible

https://github.com/fredZen/asdf-babashka/pull/5

out of curiosity, why run bb from asdf?

i use asdf for managing some things where i actually need different versions, but for bb i pretty much treat it like im always running edge

and i don’t want the asdf shims to eat any startup time

(which can sometimes be rather significant, if you’re running a lot of things)

from my perspective: I just want packages that people use to install bb to work and not be neglected

oh, yeah, i wasn’t saying we shouldn’t make asdf do the right thing

i was just curious about bb via asdf in particular given asdf, for me anyway, is a way to manage multiple versions of various things, and for bb i imagine most people treat it like “latest, please”

though i may be incorrect in that assumption

We install bb via asdf because we do the same for Java, clojure, node, python, ruby etc

Is it possible to report this babashka asdf plugin as inactive and maybe propose a more maintained one?

We've already forked at least one plugin, it's fairly straightforward

but this plugin is included in asdf by default

there must be a way to report inactive things that are included by default?

wait a minute

looks like we (Pitch) actually forked asdf-babashka to make it work on m1

https://github.com/mkarp/asdf-babashka 😂

to be used like this

asdf plugin add babashka 

that explains why we have no problems with it

what makes you say that fredZen's plugin is included in asdf by default?

I assumed so because of this: https://github.com/asdf-vm/asdf-plugins/blob/master/plugins/babashka

I'll add mkarp's fork to the bb README

ah, gotcha

if you give us a minute, we can fork it properly tomorrow in the pitch github org

ok

thanks :)

then it's easier to keep it updated than on a private repo

makes sense

so much progress, it's amazing

Perhaps the clerk + bb pull request? https://github.com/nextjournal/clerk/pull/232 cc @U5H74UNSF

@U06GMV0B0 This is a really light solution that works with bb too: https://www.loop-code-recur.io/live-clojure-cookbooks/

Live clojure cookbook Looks interesting but i’m still missing out on the interactivity.

looking at the clerk+bb request but not sure how i’d build it and use it

Are you looking for a low memory interactive process? VSCode is too heavy with the bb nREPL? Emacs?

What you could also do is start the nREPL server on your low resource machine and then connect to it from a stronger machine

tailscale works great for making your machine accessible to other machines

tailscale sounds amazing going to try that out right now

if your machine lives inside your house, you probably don't even need it btw

just open the nrepl on 0.0.0.0:1337 and then connect to your machine's IP on that port

Ended up using http://enclave.io instead of tailscale. Thanks @U04V15CAJ.