This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-11
Channels
- # announcements (38)
- # babashka (5)
- # beginners (26)
- # calva (26)
- # cider (1)
- # clj-kondo (36)
- # cljdoc (17)
- # cljs-dev (31)
- # clojure (39)
- # clojure-australia (9)
- # clojure-berlin (2)
- # clojure-dev (31)
- # clojure-europe (22)
- # clojure-france (3)
- # clojure-italy (7)
- # clojure-nl (5)
- # clojure-norway (5)
- # clojure-spec (28)
- # clojure-uk (9)
- # clojured (20)
- # clojurescript (24)
- # community-development (2)
- # conjure (32)
- # core-async (7)
- # cryogen (6)
- # datomic (2)
- # duct (6)
- # fulcro (6)
- # graalvm (53)
- # introduce-yourself (2)
- # jobs (2)
- # luminus (2)
- # nrepl (2)
- # off-topic (35)
- # re-frame (17)
- # reveal (8)
- # shadow-cljs (27)
- # testing (2)
- # xtdb (8)
A non-Clojure job in the #jobs channel: https://clojurians.slack.com/archives/C05006WDW/p1623355402112500 but seems to be in good faith. Does it make sense to have a functional jobs channel where such non-Clojure jobs can be advertised?
I think this one is properly marked as non-clojure and still relevant for Clojurians. On the broader question, yeah I think that might make sense. Even if I think the fragmentation might not be worth it. I mean, it is already a bit fragmented with #jobs and #remote-jobs. Might be better with just #jobs and that people are encourage to “tag” with remote
, non-clojure
, US
, etcetera?
➕ 20