This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-09
Channels
- # aleph (21)
- # architecture (5)
- # boot (25)
- # cider (1)
- # cljs-dev (115)
- # clojure (59)
- # clojure-brasil (3)
- # clojure-dev (4)
- # clojure-italy (20)
- # clojure-nl (2)
- # clojure-portugal (6)
- # clojure-russia (12)
- # clojure-spec (43)
- # clojure-uk (37)
- # clojurescript (76)
- # datomic (123)
- # emacs (3)
- # graphql (2)
- # hoplon (5)
- # jobs-discuss (1)
- # jobs-rus (4)
- # keechma (7)
- # lein-figwheel (13)
- # leiningen (7)
- # lumo (2)
- # off-topic (17)
- # om (6)
- # onyx (26)
- # parinfer (19)
- # planck (2)
- # re-frame (80)
- # reagent (9)
- # ring (1)
- # spacemacs (45)
- # testing (1)
- # vim (28)
Hey all, I'm starting a new Clojure(Script) project and am wondering if there's something like an up-to-date guide to making major architectural decisions in the cl(js) space?
e.g. for web server architecture, it seems duct
is becoming a good alternative to traditional ad-hoc approaches (`arachne`'s future being uncertain). For front-end, re-frame
, re-natal
are must-see; and for client/server, GraphQL and Lacinia
look capable (promising to solve a lot of typical problems with REST). etc
@limist for front end & backend api. Think fulcro is just amazing (unified backend & frontend) no need for graphql :)