This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-16
Channels
- # aleph (73)
- # babashka (12)
- # beginners (17)
- # calva (9)
- # clerk (8)
- # clj-otel (1)
- # clojars (8)
- # clojure (3)
- # clojure-europe (13)
- # clojure-nl (3)
- # clojure-norway (66)
- # clojure-uk (3)
- # clojuredesign-podcast (2)
- # clojurescript (11)
- # clr (8)
- # conjure (2)
- # core-typed (1)
- # data-science (11)
- # datahike (4)
- # etaoin (5)
- # events (1)
- # graalvm (2)
- # honeysql (27)
- # hyperfiddle (26)
- # introduce-yourself (3)
- # lsp (3)
- # membrane (1)
- # off-topic (60)
- # polylith (20)
- # practicalli (4)
- # reitit (3)
- # shadow-cljs (18)
- # specter (2)
- # xtdb (1)
Good morning!
Actually, apropos of the image above: are you really using all of the tools that you could be using in your Clojure development? I'm humbled to say that I am not. I've slept on a bunch of stuff and I'm learning currently. One big thing is VSCode - I'm already very comfortably using two main editors (Cursive and nvim), so it's a bit of a mouthful to get started on that, and the benefits are not immediately visible to me, other than that people really seem to like it.
i tried VSCode for Clojure/Script a while back and went back to emacs after a couple of weeks... i found VSCode's use of different UI idioms for different tasks quite jarring compared to emac's everything-is-a-buffer approach
otoh i tried to get emacs set up for typescript and after a bunch of effort didn't get it working very well, whereas VSCode just-works™, so i've ended up using it for typescript
Thanks everyone for the brain dump! 🧠
måning