This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-29
Channels
- # architecture (14)
- # beginners (184)
- # boot (25)
- # cider (23)
- # clara (9)
- # cljsjs (13)
- # cljsrn (5)
- # clojure (140)
- # clojure-austria (1)
- # clojure-dev (24)
- # clojure-greece (15)
- # clojure-italy (7)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-sanfrancisco (10)
- # clojure-spec (39)
- # clojure-uk (28)
- # clojured (1)
- # clojurescript (26)
- # core-async (3)
- # cursive (13)
- # datomic (44)
- # docs (3)
- # emacs (31)
- # events (2)
- # figwheel (4)
- # fulcro (6)
- # graphql (2)
- # hoplon (5)
- # jobs (11)
- # juxt (4)
- # keechma (19)
- # leiningen (1)
- # off-topic (8)
- # om (8)
- # onyx (18)
- # parinfer (2)
- # re-frame (18)
- # reagent (24)
- # ring (4)
- # rum (2)
- # shadow-cljs (26)
- # sql (15)
- # timbre (6)
- # vim (2)
https://medium.com/@conrad_9565/lets-build-a-ui-with-qlkit-and-graph-queries-79b7b118ddac looks pretty nice 🙂
I looked at it briefly. The main difference between om/fulcro seemed to be simplicity and a different query syntax, at the cost of the entire tree re-rendering on every parse?
Any reason I might use it over om/fulcro (as someone who doesn't consider those overly complex)?
For very simple applications, I sometimes reach for rum instead.
@danielstockton Rearding about it now also. Seems pretty interesting and think it's really cool that there are other om-next inspired arhitectures. They also have page in the wiki section detailing om-next differences https://github.com/forward-blockchain/qlkit/wiki/Differences-from-Om-Next
Yes, it's definitely good to have different alternatives.