This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-15
Channels
- # announcements (11)
- # beginners (66)
- # boot (6)
- # clara (25)
- # cljdoc (4)
- # cljs-dev (22)
- # clojure (261)
- # clojure-dev (1)
- # clojure-europe (2)
- # clojure-italy (15)
- # clojure-losangeles (1)
- # clojure-nl (19)
- # clojure-spec (62)
- # clojure-uk (50)
- # clojurescript (12)
- # community-development (6)
- # cursive (60)
- # datomic (21)
- # emacs (2)
- # figwheel (2)
- # figwheel-main (3)
- # fulcro (2)
- # graphql (11)
- # hyperfiddle (11)
- # javascript (1)
- # jobs (6)
- # juxt (1)
- # kaocha (5)
- # keechma (2)
- # off-topic (4)
- # onyx (10)
- # pathom (7)
- # re-frame (15)
- # reagent (8)
- # remote-jobs (2)
- # ring-swagger (14)
- # shadow-cljs (35)
- # sql (22)
- # testing (9)
- # tools-deps (62)
- # vim (12)
I can see how https://clojurians.zulipchat.com/ would be favored over Slack by folks who prefer keyboard navigation. At first I found the streams and topic UI very "busy", especially with all the colors being used, but I've quickly gotten used to it, and I'm loving the keyboard navigation! I'd encourage more folks <!here> to try out Zulip, if you still harbor concerns about Slack.
I'll second that. Topics are a really big win.
For those who missed the announcement yesterday: I wrote an article with the details and rationale at ClojureVerse: https://clojureverse.org/t/introducing-clojurians-zulip/3173
Streams and topics take some getting used to after Slack but I definitely feel they're a better solution than threads (in Slack).
i may change my mind @U04V70XH6 but for the moment i prefer the decide-later notion of threads - i.e. you can decide to thread something of your own or someone else at some time after it was written, no need to decide in advance
For those who missed the announcement yesterday: I wrote an article with the details and rationale at ClojureVerse: https://clojureverse.org/t/introducing-clojurians-zulip/3173