This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-12
Channels
- # announcements (4)
- # asami (3)
- # babashka (18)
- # babashka-sci-dev (2)
- # beginners (55)
- # calva (18)
- # clj-commons (23)
- # clj-kondo (2)
- # cljfx (7)
- # cljs-dev (15)
- # clojure (96)
- # clojure-europe (43)
- # clojure-losangeles (3)
- # clojure-nl (2)
- # clojure-uk (11)
- # clojurescript (1)
- # datalevin (2)
- # datomic (10)
- # events (1)
- # google-cloud (4)
- # gratitude (16)
- # helix (3)
- # hyperfiddle (63)
- # inf-clojure (13)
- # introduce-yourself (4)
- # ipfs (2)
- # jobs (2)
- # jobs-discuss (12)
- # leiningen (7)
- # lsp (15)
- # off-topic (38)
- # polylith (24)
- # portal (27)
- # remote-jobs (8)
- # sci (27)
- # spacemacs (5)
- # specter (1)
- # sql (5)
- # xtdb (41)
@seancorfield I saw your dot-clojure uses eastwood. I just checked the docs of eastwood, seems most functionalities are covered by clj-kondo. Would like to know your use case on it.
Historical, really. HoneySQL has Eastwood as part of its CI pipeline. I use clj-kondo "live" in my editor for stuff but haven't taken the time to figure out how to tune it for use in CI, whereas Eastwood is pretty easy for that -- although I only use Eastwood on that one project (and probably wouldn't use it if it weren't already setup when I inherited HoneySQL).
