This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-23
Channels
- # admin-announcements (6)
- # aleph (3)
- # beginners (38)
- # boot (119)
- # braid-chat (15)
- # braveandtrue (1)
- # clara (4)
- # cljs-dev (56)
- # cljsfiddle (12)
- # cljsjs (15)
- # cljsrn (6)
- # clojars (4)
- # clojure (113)
- # clojure-art (1)
- # clojure-berlin (1)
- # clojure-dusseldorf (3)
- # clojure-india (15)
- # clojure-new-zealand (3)
- # clojure-poland (1)
- # clojure-russia (83)
- # clojure-uk (18)
- # clojurescript (97)
- # community-development (9)
- # cursive (1)
- # data-science (1)
- # datomic (12)
- # emacs (14)
- # hoplon (350)
- # immutant (2)
- # jobs (2)
- # jobs-discuss (23)
- # keechma (74)
- # liberator (1)
- # off-topic (1)
- # om (127)
- # onyx (54)
- # parinfer (74)
- # pedestal (1)
- # proton (5)
- # re-frame (6)
- # reagent (4)
- # remote-jobs (17)
- # ring-swagger (1)
- # slack-help (5)
- # untangled (16)
- # yada (21)
@xlevus: yes… error message is one of the worst feature of Clojure. I think most people agree with that.
for me; refactoring
utter nightmare
@glenjamin: nope, equally bad
@martintrojer: do you think that is due to the fact that it is dynamically typed?
they are all so bad, the differences are in the noise
although I do think to some extent the very effective refactoring tools in javaland can lead to APIs / Interfaces not being thought through
we’re at ~60% tests. Still, refactoring bugs show up weeks later in prod
Its chipping away at my sanity
don’t know how much more I can take of this 😞
this is with ~5year Clojure experience