This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-01
Channels
- # announcements (4)
- # aws (1)
- # beginners (172)
- # cider (16)
- # cljdoc (63)
- # cljsrn (7)
- # clojure (150)
- # clojure-dev (8)
- # clojure-europe (26)
- # clojure-gamedev (6)
- # clojure-greece (23)
- # clojure-nl (4)
- # clojure-spec (10)
- # clojure-uk (101)
- # clojurescript (40)
- # community-development (5)
- # cursive (19)
- # datomic (54)
- # emacs (39)
- # figwheel-main (5)
- # fulcro (4)
- # graphql (16)
- # immutant (5)
- # jobs (8)
- # jobs-rus (1)
- # leiningen (1)
- # off-topic (31)
- # planck (1)
- # re-frame (7)
- # reagent (8)
- # reitit (6)
- # remote-jobs (4)
- # shadow-cljs (11)
- # spacemacs (18)
- # specter (2)
- # sql (58)
- # vim (2)
- # yada (5)
Also I can see someone using Bidi on the CLJS side (probably with Accountant or similar) and then using something else(tm) (i.e. Compojure) on the back end...
yeah actually after posting it i took a look and we're not using compojure anymore, only bidi ๐
My, personal, front end experience is Reagent with Bidi + Accountant, but I am starting to agree with the Reframe story if the app is big / complex enough to merit the extra hoop-jumping.
I moved from bidi back to compojure in the last thing I built, but I was a very, uh, early adopter of bidi
@maleghast would you go reframe on the FE now then?
@otfrom - I am sorry, on a call. TLDR; if it's more than 3 or 4 views or the data model is complex I would go to re-Frame, but there is a flexibility benefit to not using it if the use-case is simple.
Also Bidi has gotten really good, imho, but the documentation is still hard to follow (Dom and Malcolm are both in agreement here, I am not saying anything contraversial), so getting going can be hard work...
@otfrom did you see reitit? I have a positive experience with personal projects with it