This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-11
Channels
- # aleph (3)
- # beginners (42)
- # cider (219)
- # cljs-dev (39)
- # cljsjs (19)
- # cljsrn (3)
- # clojure (97)
- # clojure-canada (12)
- # clojure-dev (14)
- # clojure-italy (5)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-spec (3)
- # clojure-uk (140)
- # clojurescript (52)
- # clojutre (2)
- # cursive (2)
- # datomic (29)
- # docs (1)
- # duct (13)
- # emacs (19)
- # fulcro (8)
- # funcool (2)
- # graphql (26)
- # hyperfiddle (1)
- # luminus (9)
- # nyc (7)
- # off-topic (26)
- # om (21)
- # onyx (19)
- # overtone (1)
- # pedestal (4)
- # re-frame (10)
- # reagent (109)
- # ring (5)
- # rum (15)
- # shadow-cljs (120)
- # spacemacs (22)
- # specter (7)
- # vim (10)
This project looks promising. Thank you for putting this together, I spend a fair amount of time thinking about how to make systems more clear, as i believe, the better you can express what your system is supposed to to do, the more likely it does just that 🙂. Articles seems very similar to literate programming. I find it strange that you don’t mention the idea anywhere in your docs. Is there a reason for this? For example here is a literate clojure effort: https://github.com/stardiviner/ob-clojure-literate I would also argue that maria tries to deliver on this: https://github.com/mhuebert/maria I feel the idea of creating a narrative around the code is crucial and I have written a little bit about it here. Though i have done any real work like you 🙂. https://github.com/drewverlee/narrative