This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-06-14
Channels
- # biff (2)
- # calva (1)
- # clj-kondo (1)
- # clj-otel (34)
- # clojure (49)
- # clojure-europe (44)
- # clojure-nl (2)
- # clojure-norway (21)
- # clojure-sweden (11)
- # clojure-uk (6)
- # clojurescript (7)
- # data-science (3)
- # datahike (34)
- # emacs (17)
- # fulcro (1)
- # gratitude (5)
- # honeysql (1)
- # jobs (11)
- # leiningen (42)
- # lsp (5)
- # nextjournal (3)
- # observability (1)
- # practicalli (2)
- # shadow-cljs (153)
- # solo-full-stack (5)
- # squint (7)
- # xtdb (16)
I’ve been using Clojure for over 10 years, and I remember when things weren’t as polished as they are now. Today, I deeply appreciate the modern state of tools we have at our disposal: clj-kondo, clojure-lsp, paredit plugins for editors, tools.build, tools.deps, and more. Now that I’m learning a new language, I realize just how spoiled we’ve become with these fantastic tools. The LSP support might not be as stable, and the editor integration isn’t as seamless, making me truly grateful for the refined and well-supported ecosystem we have in Clojure. These little conveniences, which we often take for granted, really highlight how much the Clojure community has optimized our development experience. Special thanks to (in random order): @ericdallo, @borkdude, @alexmiller, @pez, and all other library writers and maintainers. Thank you to everyone who’s contributed to making Clojure such a joy to work with!

I've been looking statically typed language which supports old platforms (e.g. win xp and friends) with good cross-compilation capabilities (my dev machine is mac). Stumbled upon Nim. It also focuses on getting stuff done instead of code-golfing approach.