This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-07-20
Channels
- # announcements (26)
- # babashka (1)
- # beginners (15)
- # biff (6)
- # cider (3)
- # circleci (1)
- # clj-kondo (33)
- # clojure (23)
- # clojure-denver (13)
- # clojure-europe (22)
- # clojure-norway (2)
- # clojurescript (45)
- # conjure (2)
- # datascript (4)
- # datomic (8)
- # events (5)
- # ghostwheel (2)
- # gratitude (4)
- # hyperfiddle (5)
- # jobs (5)
- # music (1)
- # off-topic (19)
- # pathom (4)
- # portal (25)
- # reitit (4)
- # releases (1)
- # shadow-cljs (28)
- # specter (2)
- # xtdb (23)
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-symbol
• https://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
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 !
@U04V15CAJ grammar nitpick: “fast-starting” should be hyphenated.
Whoa nice, TIL that Babashka has timbre
and simple web server stuff built in!
What's the expected use case for say using hiccup
in this way?
@U058DHAN3UP You can see an example of a babashka web app with hiccup here: https://github.com/kloimhardt/babashka-scittle-guestbook
Thanks, good to know one could whip up quick servers in a pinch!
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.
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 😁
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.
> I was at the point where I just had to get the thing out the door Heh, I know that feeling all too well 😂
A long way from greatness, but definitely better: https://www.youtube.com/watch?v=sjxPj7DqUSs
> 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!
(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 🙂)
@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.
> 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. 😅
> (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?
I'd assume so, will try to check that today but work is a bit crazy currently so may not get time.
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.
Also kudos to @U066U8JQJ for using it in Pathom, that’s how we found out about guardrails!
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.