This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-23
Channels
- # adventofcode (135)
- # announcements (9)
- # babashka (27)
- # beginners (97)
- # bristol-clojurians (8)
- # calva (7)
- # chlorine-clover (1)
- # cider (3)
- # clara (16)
- # clj-kondo (9)
- # cljdoc (137)
- # clojars (4)
- # clojure (110)
- # clojure-europe (118)
- # clojure-taiwan (8)
- # clojure-uk (19)
- # clojurescript (30)
- # conjure (6)
- # cryogen (32)
- # datomic (11)
- # depstar (1)
- # duct (4)
- # emacs (6)
- # fulcro (73)
- # graalvm (9)
- # keechma (7)
- # leiningen (16)
- # luminus (1)
- # malli (35)
- # meander (3)
- # off-topic (45)
- # pathom (1)
- # pedestal (2)
- # re-frame (3)
- # reagent (31)
- # reitit (2)
- # reveal (17)
- # shadow-cljs (34)
- # tools-deps (11)
- # xtdb (14)
Dang @borkdude, every now and then, after clj-kondo instantly tells me I’ve got something wrong, I sit back and marvel at how helpful it is. What an awesome feedback loop!
Even though I have created it mostly myself, I can't help getting the same feeling from time to time, haha
I'll +100 that. I've gotten so used to clj-kondo spotting mistakes that sort take for granted that it's there: I just sort of expect my "editor" to point stuff out now and when I have to work on non-Clojure code it's so frustrating that stupid mistakes don't show up immediately! 🙂
I like that clj-kondo is not judgmental of the number of stupid mistakes I make. It just gently says, “hey buddy, you might not want to do that”.
I'm currently working on a fork which remembers your failures and tweets them to make you feel bad.
Me too, clj-kondo is a great tool, grateful for it every day. Particularly grateful that it supports babashka.process
's $
macro as I'm using that a lot these days.