This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-12
Channels
- # admin-announcements (1)
- # arachne (3)
- # cider (11)
- # cljsrn (5)
- # clojure (26)
- # clojure-android (10)
- # clojure-greece (8)
- # clojure-russia (5)
- # clojure-spec (7)
- # clojure-uk (3)
- # clojurescript (16)
- # clojurex (38)
- # core-async (1)
- # css (3)
- # cursive (42)
- # dirac (2)
- # hoplon (28)
- # keechma (1)
- # lein-figwheel (2)
- # leiningen (1)
- # mount (3)
- # om (132)
- # onyx (46)
- # re-frame (53)
- # reagent (17)
- # spacemacs (7)
- # specter (50)
- # untangled (2)
- # yada (3)
Wow, I go to a Java conference for 3 days & the community I love starts a big internal spat http://ashtonkemerling.com/blog/2016/06/11/my-increasing-frustration-with-clojure/ Also we get a date clash with Conf and ClojureX that then turns into the opportunity for a transatlantic Clojure party! What will happen when I'm on holiday in August!?
I must admit I feel reticent to raise issues in Clojure's JIRA, but more from a complete lack of understanding of the data science around design decisions and the unwillingness to look like an idiot 😕
I would agree with one theme in that post, anything that can be done to decrease the cognitive load required to determine what is 'legal and sensible' to pass to a function and make it's intent more explicit is a good thing. Hence I like Schema and have high hopes for Spec and that I do wish we had a decent type inference system in Clojure. One of my favourite parts of Clojure is that it makes most state change explicit and obvious, it's a shame it doesn't always make other aspects of the language like laziness and 'sane' argument types so explicit.