This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-08
Channels
- # aleph (11)
- # arachne (7)
- # aws (1)
- # bangalore-clj (4)
- # beginners (24)
- # boot (128)
- # bristol-clojurians (23)
- # cider (1)
- # cljs-dev (43)
- # cljsrn (6)
- # clojure (178)
- # clojure-austin (3)
- # clojure-chicago (1)
- # clojure-dusseldorf (14)
- # clojure-finland (15)
- # clojure-france (6)
- # clojure-italy (18)
- # clojure-portugal (2)
- # clojure-russia (67)
- # clojure-spec (148)
- # clojure-uk (55)
- # clojurescript (199)
- # core-async (4)
- # cursive (18)
- # datascript (5)
- # datomic (120)
- # devcards (3)
- # dirac (53)
- # emacs (11)
- # events (3)
- # gsoc (7)
- # jobs (1)
- # lein-figwheel (25)
- # leiningen (5)
- # lumo (12)
- # off-topic (29)
- # om (174)
- # om-next (2)
- # onyx (7)
- # perun (10)
- # protorepl (6)
- # re-frame (12)
- # remote-jobs (1)
- # ring (19)
- # ring-swagger (25)
- # rum (6)
- # spacemacs (13)
- # sql (3)
- # untangled (88)
- # yada (7)
@stbgz: I started experimenting to see what a good cljs tool might look like on Node
for the parts that are not possible in Node yet, I shell out to Java
just to focus on the UX, so we can replace the parts with Node as they came
Lumo happened, so I put that in. your dep resolver isn’t fully compatible yet, so I had to leave it out for now
the worst part about leaving the jvm is not having figwheel
project is ~300 lines of cljs/clj, all the hard work is done elsewhere
@shaunlebron that’s great I am on the same boat.. like @anmonteiro said we should definitely pool our efforts it seems there are a few us trying to build something similar
I spent some time looking at cljs.closure
I think our challenge is going to be transforming that file to a cljc
file
nice job w/ calvin: https://github.com/eginez/calvin