This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-31
Channels
- # bangalore-clj (3)
- # beginners (15)
- # boot (128)
- # cider (4)
- # cljs-dev (12)
- # cljsjs (1)
- # clojure (105)
- # clojure-austin (5)
- # clojure-canada (6)
- # clojure-italy (5)
- # clojure-russia (14)
- # clojure-spec (70)
- # clojure-uk (21)
- # clojurebridge (3)
- # clojurescript (264)
- # cloverage (6)
- # cursive (4)
- # data-science (6)
- # datomic (10)
- # dirac (5)
- # editors (30)
- # events (3)
- # hoplon (9)
- # klipse (7)
- # leiningen (3)
- # luminus (4)
- # off-topic (9)
- # om (5)
- # om-next (1)
- # onyx (1)
- # parinfer (2)
- # perun (28)
- # re-frame (5)
- # ring (1)
- # rum (11)
- # spacemacs (2)
- # specter (10)
- # sql (3)
- # uncomplicate (4)
- # untangled (67)
- # vim (2)
- # yada (1)
@mynomoto: sorry I just meant that the server demos would have both client and server stuff for the same project
It would be nice to pick a common server task for all the demos
@flyboarder don't worry, it's cool. I certainly agree that the server demos should have everything in the same project. You mean a common server task for demos with server code (like the castra ones)?
Exactly, just to stabilize the deps
Yeah, I don't really use that setup anywhere else, only made it work when converting it to use the serve task. Not sure of what would be best for the demos.
Maybe use the tailrecursion one? Does it have the same issue?