This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-18
Channels
- # adventofcode (62)
- # aws (5)
- # beginners (59)
- # calva (63)
- # cider (26)
- # cljdoc (1)
- # cljsrn (22)
- # clojure (99)
- # clojure-austin (1)
- # clojure-dev (19)
- # clojure-europe (4)
- # clojure-hamburg (2)
- # clojure-italy (3)
- # clojure-nl (23)
- # clojure-spec (2)
- # clojure-uk (85)
- # clojurescript (41)
- # core-async (17)
- # cursive (20)
- # data-science (11)
- # datascript (2)
- # datomic (31)
- # emacs (7)
- # figwheel (28)
- # figwheel-main (12)
- # graphql (2)
- # hyperfiddle (3)
- # juxt (1)
- # kaocha (2)
- # leiningen (5)
- # nrepl (13)
- # off-topic (45)
- # pathom (13)
- # pedestal (11)
- # re-frame (20)
- # reagent (10)
- # shadow-cljs (92)
- # spacemacs (9)
- # sql (39)
- # tools-deps (32)
- # unrepl (3)
Is there any “official” docker image for clojurescript + node + clojure cmd instead lein ?
announcing this new npm library for react-native https://github.com/bhauman/react-native-figwheel-bridge
I’m taking the “runtime interpretation, possibly slow templates” approach right now 😛
but it is incredibly interesting. I went down the macro hole earlier this year and like he outlines in the article, found it frustrating and dangerous for new users to figure out what was interpreted vs. not
I could play some tricks to get certain things to compile but then that just ended up being even more confusing when it didn’t
yeah, I was thinking about last night how best to do a benchmark of the actual cost of the runtime hiccup interpretation vs compilation
and I wonder how it changes with large trees of shallow components (so you’re calling the interpreter many many times) vs. deep components, shallower total tree
I’ll play with this more today. I have a project that I’m going completely into outer space with; using hx + a fork of re-frame, [email protected] and hooks, all the new toys.