This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-02
Channels
- # aleph (3)
- # announcements (2)
- # babashka (4)
- # beginners (74)
- # calva (21)
- # clj-kondo (30)
- # cljs-dev (7)
- # cljsrn (42)
- # clojure (121)
- # clojure-dev (13)
- # clojure-europe (23)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-norway (7)
- # clojure-spec (140)
- # clojure-uk (58)
- # clojuredesign-podcast (9)
- # clojurescript (49)
- # clojutre (2)
- # cursive (32)
- # datascript (2)
- # datomic (59)
- # duct (7)
- # figwheel-main (6)
- # fulcro (18)
- # graphql (5)
- # jackdaw (1)
- # joker (6)
- # juxt (7)
- # leiningen (9)
- # off-topic (1)
- # pedestal (14)
- # quil (2)
- # re-frame (3)
- # reitit (8)
- # shadow-cljs (78)
- # sql (8)
- # timbre (3)
- # vim (69)
I finally got a first sort-of working version of the "Twitter Poster" series (episodes 21-27). I would love to hear some feedback: https://github.com/jumarko/functional-design-in-clojure/pull/5 Cc: @nate
As a side note, it would be interesting to actually see the implementation of the worker
and decider
multimethods and how is that different from the usual approach IO -> logic -> IO -> logic -> ...
This stuff is quite hard to grasp without looking at code I think.
Related video from LambdaIsland is here (still need to watch it): https://www.youtube.com/watch?v=loDf8Pk4kD4&feature=youtu.be
@U06BE1L6T Yes, speaking code is pretty tough, and I'd like to eventually release more code to illustrate IO -> logic -> IO -> logic. Currently all our code that takes that approach is tied up in proprietary code bases for our clients.
Now I know what felt so wrong with all those Clojure band names. They weren’t Hall of Oats! https://github.com/cognitect-labs/anomalies
@U0ETXRFEW That's too funny!