This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-01
Channels
- # aleph (1)
- # bangalore-clj (5)
- # beginners (24)
- # boot (113)
- # cider (42)
- # cljs-dev (2)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (37)
- # clojure-austin (4)
- # clojure-brasil (3)
- # clojure-france (55)
- # clojure-greece (15)
- # clojure-ireland (4)
- # clojure-italy (13)
- # clojure-russia (37)
- # clojure-spec (50)
- # clojure-uk (31)
- # clojurescript (49)
- # component (12)
- # consulting (1)
- # cursive (6)
- # datascript (9)
- # datomic (27)
- # editors (2)
- # garden (1)
- # hoplon (18)
- # jobs (1)
- # klipse (25)
- # lein-figwheel (1)
- # leiningen (1)
- # luminus (2)
- # om (53)
- # om-next (8)
- # onyx (5)
- # parinfer (4)
- # perun (4)
- # re-frame (13)
- # remote-jobs (1)
- # ring (1)
- # ring-swagger (3)
- # rum (52)
- # spacemacs (36)
- # specter (13)
- # sql (3)
- # untangled (49)
- # vim (11)
- # yada (9)
@jasonjckn Wow this is awesome. Do you have support for Docker containers?
Awesome. Do you have an example in a repo I could check out?:)
@keatondunsford: I use Duct prodigiously – it’s built on Ring and Compjure. Wouldn’t go back. Ring, as I understand it, is getting async support (if it hasn’t already?), which is Pedestal’s principle advantage. Ring’s advantage is having a wealth of middleware that supports it. And, it’s so simple.
And a side note… If you just have to have Clojurescript on the front-end, personally, I’d try using reagent all on its own, with an upgrade path to re-frame or one of the supporting tools.
@yogthos, I think has made a great case for that path (as opposed to Om): https://www.reddit.com/r/Clojure/comments/2xi4ft/how_to_structurize_a_clojurescriptreagent/
I spent a month working with Om.Next, and frankly, it was hard, and there was too little benefit for the costs.