Fork me on GitHub
#announcements
<
2023-07-20
>
borkdude09:07:06

https://github.com/babashka/babashka: Native, fast starting Clojure interpreter for scripting 1.3.182 (2023-07-20) • https://github.com/babashka/babashka/issues/1579: add clojure.tools.reader/resolve-symbolhttps://github.com/babashka/babashka/issues/1581: bb print-deps: sort dependencies (https://github.com/teodorlu) • Upgrade babashka.http-client to 0.4.12, fixes :insecure option • Bump https://github.com/borkdude/edamame to 1.3.23: fixes infinite loop with reader conditional expression • Bump https://github.com/yogthos/Selmer to Bumping to 1.12.59 • Bump https://github.com/borkdude/deps.clj with more fixes which should make downloading/installation of tools jar more robust • Add .ssl.X509ExtendedTrustManager class • Bump https://github.com/babashka/process: accept path or file as :dir argument • Bump https://github.com/weavejester/hiccup to 2.0.0-RC1 Thanks for the support gratitude !

10
babashka 48
🎉 14
gratitude 12
❤️ 6
catjam 4
wevrem00:07:49

@U04V15CAJ grammar nitpick: “fast-starting” should be hyphenated.

Colin (fosskers)01:07:23

Whoa nice, TIL that Babashka has timbre and simple web server stuff built in!

Colin (fosskers)01:07:49

What's the expected use case for say using hiccup in this way?

borkdude08:07:55

@U058DHAN3UP You can see an example of a babashka web app with hiccup here: https://github.com/kloimhardt/babashka-scittle-guestbook

Colin (fosskers)09:07:59

Thanks, good to know one could whip up quick servers in a pinch!

gnl17:07:51

Hey everyone, I haven't been around these here parts in a while, but I have now returned with not one, but TWO announcements, the first one being a long overdue status update on Ghostwheel, which I'm sure everyone thought long dead and buried, but they'd be wrong! So wrong. Which is to say that yes, TL;DR, it is in fact dead, but (most of) its parts live on in beautiful synergistic independence. https://github.com/gnl/ghostwheel/blob/master/STATUS.adoc.

🔥 20
🎉 8
eggsyntax21:07:41

Hooray!

🙌 2
eggsyntax21:07:47

This is awesome! I'd totally missed Guardrails somehow, and I'm really looking forward to playing with Playback! I hate to say it but I think the Playback screencast is really confusing, mainly because the number of windows that are open and undergoing change made it really unclear what I should be looking at. I think the use of (presumably Guardrails?) typing on foo will also throw some people off. Personally I think your best option would be to hide the nREPL entirely, and put the rich comments in the same window as the definition of foo, so that you really only have two windows active at a time. Some narration might really help too, but with just two windows I think you could get away without it. Hope that's helpful. Any confusion I may have had was far outweighed by excitement about Guardrails and Playback 😁

👆 2
gnl22:07:21

No, you're totally right, it's horrible! :D I was at the point where I just had to get the thing out the door, but yeah, way too much going on. The nREPL hiding is a good idea, I was thinking that too. Will definitely redo it in the not too far future, hopefully already over the next days.

gnl22:07:06

Added a note to the YouTube video, but yeah, definitely needs redoing.

eggsyntax22:07:17

> I was at the point where I just had to get the thing out the door Heh, I know that feeling all too well 😂

gnl22:07:41

When you get a chance to play around with it, let me know how it goes!

gnl01:07:41

A long way from greatness, but definitely better: https://www.youtube.com/watch?v=sjxPj7DqUSs

👍 2
Stefan14:07:32

We've been using Guardrails in our product for a while now, I love it!

eggsyntax15:07:59

> A long way from greatness, but definitely better: Ah, yeah, that definitely seems clearer to me! I'd still lean toward either removing the window/section with the rich comment (in favor of putting the rich comment in the same buffer as the defn), or use the mouse to switch between upper-left and lower-left, because it's a bit hard for my eye to notice when the blinking cursor switches windows. But that's just a suggestion, it already seems way clearer to me!

eggsyntax15:07:42

(filed an issue on the repo, btw -- I got an error when I tried to incorporate playback into a clojure-only project. NBD of course, just wanted to let you know 🙂)

gnl16:07:41

@UGNFXV1FA I love that it's collecting kudos-by-proxy for me 😁 I'm really glad Tony picked it up and took as good care of it as he did when I fell off the radar, and kept the hope alive that we'll be seeing widespread gspecs throughout all kinds of codebases at some point in the future.

gnl16:07:34

> use the mouse to switch between upper-left and lower-left That occurred to me right after I'd finished publishing the new version and I decided to get over my tendency to fiddle beyond a reasonable point and not redo it this time, much as it pained me. 😅

💯 2
gnl16:07:51

> (filed an issue on the repo, btw -- I got an error when I tried to incorporate playback into a clojure-only project. NBD of course, just wanted to let you know I assume this goes away if you add ClojureScript to your dev dependencies?

eggsyntax16:07:32

I'd assume so, will try to check that today but work is a bit crazy currently so may not get time.

eggsyntax16:07:57

Yep, confirmed.

gnl16:07:34

Cool, thanks, I replied to https://github.com/gnl/playback/issues/1 to keep the conversation in one place. TL;DR – I'm okay solving this with a hammer instead of a scalpel.

👍 2
😆 2
Stefan08:07:37

Also kudos to @U066U8JQJ for using it in Pathom, that’s how we found out about guardrails!

🙌 2
gnl17:07:38

The second one is my new open-source project: https://github.com/gnl/playback/ There's a short screencast, but in the 3 minutes it takes to watch, you might just be up and running with the actual library. If you like it, come upvote the https://news.ycombinator.com/item?id=36803438, so I can make the front page and get eyeballs and internet points.

🎉 22
👍 4