This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-25
Channels
- # architecture (12)
- # asami (6)
- # aws (2)
- # babashka (2)
- # beginners (71)
- # bristol-clojurians (1)
- # calva (1)
- # cider (2)
- # clojure (136)
- # clojure-australia (6)
- # clojure-dev (14)
- # clojure-europe (11)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-sanfrancisco (29)
- # clojure-uk (9)
- # clojuredesign-podcast (12)
- # clojurescript (23)
- # code-reviews (7)
- # core-logic (5)
- # cryogen (7)
- # datomic (7)
- # depstar (7)
- # events (3)
- # fulcro (11)
- # helix (1)
- # jobs (2)
- # juxt (4)
- # kaocha (25)
- # leiningen (2)
- # malli (11)
- # off-topic (8)
- # pathom (1)
- # pedestal (9)
- # portkey (1)
- # reitit (3)
- # ring (2)
- # sci (46)
- # shadow-cljs (21)
- # tools-deps (15)
- # xtdb (31)
Something I’ve been wondering about…. why is it necessary to have this separation into a context map and a response map. Why can’t the response map itself be treated as the context?
https://github.com/metosin/sieppari does that For pedestal, i think the reason is "history"
Interesting. I have some difficulties gauging how much of Pedestal is replaced by reitit/sieppari and possibly other metosin projects?
- they do performance in a "microbenchmark world"
- they usually prefer unqualified keys
- they use BreakVer
- they usually over-extend their interfaces to "developer easiness"
Interesting. I’m not that intimately familiar with their libraries other than spec-tools which we had a couple of uses for at my old work. My superficial impression is that they seem to be kind of intent on learning from and one-upping Cognitect with many of their libs.