This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (15)
- # babashka (143)
- # babashka-sci-dev (2)
- # beginners (35)
- # biff (11)
- # calva (5)
- # cider (8)
- # clerk (4)
- # clj-kondo (58)
- # cljdoc (6)
- # clojure (88)
- # clojure-denmark (1)
- # clojure-europe (77)
- # clojure-nl (1)
- # clojure-norway (16)
- # clojure-uk (1)
- # clojurescript (19)
- # clr (32)
- # code-reviews (158)
- # datahike (5)
- # datomic (10)
- # deps-new (3)
- # fulcro (12)
- # graalvm (20)
- # honeysql (23)
- # hyperfiddle (32)
- # jobs (1)
- # kaocha (10)
- # membrane (6)
- # observability (1)
- # other-languages (2)
- # pathom (5)
- # practicalli (12)
- # reagent (4)
- # reitit (7)
- # releases (1)
- # remote-jobs (1)
- # sci (25)
- # shadow-cljs (52)
Announcing https://github.com/beoliver/wiretap: A small library for adding custom tracing without having to modify source code.
tick 0.6.0 released. The new version works with babashka. Thanks https://github.com/dvingo and https://github.com/borkdude !
Also new is a section in the README looking at the tradeoffs of date-time API choice : https://github.com/juxt/tick#should-you-use-tick-for-date-time-work . It's a question that seems to come up on here on slack quite a bit. Opinions welcome!
Should you use Tick for date-time work?
• If you are just working on the JVM and are comfortable with the
java.time API then raw interop will work just fine.
• If you meet any of the following criteria, use https://github.com/henryw374/cljc.java-time:
◦ are creating cross-platform date-time logic
◦ are not proficient in java.time and would like https://widdindustries.com/why-not-interop/
◦ would rather not maintain type hints in your code or deal with interop syntax
• If you meet the criteria to use cljc.java-time but would like a more terse API and the benefits of e.g. https://juxt.github.io/tick/#_substitution or the interval calculus, but will not miss having every date-time recipe one google search away, then tick might be a good choice. Tick uses https://github.com/henryw374/cljc.java-time so you can always drop to that if Tick is missing something you need.
• Similar in aiming for a terse API, but jvm-only is https://github.com/dm3/clojure.java-time.
has the tag not been pushed? 🙂 I don’t see it in the repo
@U051B9FU1 I really appreciate what you’ve done with Tick and I like using it and having a common API for both Clojure and ClojureScript.
tick is great, such a pleasure to have basically identical time-related semantics in Clojure, ClojureScript and now babashka!
ClojureCLR next! 😄
malli also recently got support for java.time based schemas, makes for a really powerful combination with tick :) https://github.com/metosin/malli#malliexperimentaltime
Hey I wanted to explore the new OpenAI chatGPT API that was announced a couple days ago and I've been meaning to try out bababska so I wrote this quick little
bb cli to have an ai conversation through the terminal. I'm on linux so not sure if it will work on Mac or Windows. You can find it here: https://gist.github.com/chase-lambert/c5533d8e8fbb71268a25e83ecf8e3cc6 with the instructions in the comments. It's quite barebones but quick and fun without having to go to the OpenAI website which usually takes a while to load for me.
If you prefer a regular ole Clojure repo you can find that here: https://github.com/chase-lambert/chatgpt-cli This uses
clojure.data.json instead of bb's built in http client and
cheshire.json so the code has a few minor alterations.
The new API is crazy cheap and it's for their most powerful model. It is $0.002 for a 1000 tokens which equates to about 375,000 words for a $1.
Whether it has anything of worth to say in that massive amount of words is still up for debate.