This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-22
Channels
- # arachne (8)
- # bangalore-clj (1)
- # beginners (72)
- # boot (95)
- # braveandtrue (5)
- # business (1)
- # capetown (1)
- # cider (180)
- # cljs-dev (8)
- # cljsrn (20)
- # clojure (104)
- # clojure-art (1)
- # clojure-brasil (8)
- # clojure-czech (1)
- # clojure-greece (15)
- # clojure-korea (13)
- # clojure-poland (2)
- # clojure-russia (53)
- # clojure-sg (5)
- # clojure-spec (60)
- # clojure-uk (35)
- # clojurescript (186)
- # community-development (3)
- # core-async (24)
- # cursive (18)
- # datascript (11)
- # datomic (39)
- # devcards (4)
- # emacs (2)
- # events (1)
- # funcool (23)
- # hoplon (148)
- # juxt (1)
- # ldnclj (2)
- # luminus (1)
- # off-topic (22)
- # om (27)
- # onyx (35)
- # overtone (2)
- # pedestal (7)
- # perun (8)
- # protorepl (2)
- # rdf (6)
- # re-frame (15)
- # reagent (2)
- # ring-swagger (10)
- # untangled (54)
We have an update in the works for Wednesday. I had to pick of some work to keep the lights and got behind. Chimera will be discussed in the update.
What are the plans for arachne with the front end? For example: will I be able to make a module that defines routes for both the http module and a cljs app, so that each route is a pre-rendered entry point to the cljs app?
I haven’t put too much effort into the client side yet because (a) I think the server side is a great pain point at the moment and (b) the client side is moving so fast it’s hard to know what to target that won’t go out of style in 2 months. But Arachne is absolutely designed for that sort of thing, if someone writes an appropriate front-end module.