This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-02
Channels
- # beginners (29)
- # boot (65)
- # cider (12)
- # cljs-dev (8)
- # cljsjs (31)
- # clojars (5)
- # clojure (147)
- # clojure-austin (47)
- # clojure-berlin (1)
- # clojure-brasil (7)
- # clojure-russia (5)
- # clojure-spec (18)
- # clojure-uk (18)
- # clojurescript (113)
- # css (2)
- # cursive (7)
- # datascript (5)
- # datomic (2)
- # dirac (4)
- # events (3)
- # funcool (143)
- # hoplon (287)
- # jobs (2)
- # off-topic (4)
- # om (10)
- # om-next (5)
- # onyx (18)
- # protorepl (1)
- # re-frame (93)
- # reagent (34)
- # rum (41)
- # test-check (51)
- # untangled (15)
- # yada (18)
At a wild guess, I'd say that 60% do use re-frame and 40% don't. But that is very wild guess.
Indicative-ish
If your application is sufficiently simple, you don't need re-frame
As your application gets bigger and more complicated, you will start growing architectural decisions. You may be happy with your own, or you might want to use the approaches distilled by re-frame
Just be aware that Reagent does not supply any architecture. If is just the V bit of MVC. So you will be doing the equivalent of M and C yourself (which many are happy to do).
In defence of re-frame (I am the author): I hear the following regularly "I started Reagent 6 months ago, and completely loved it. But after a while, I got to a place I wasn't happy with." <---- the person is effectively saying "I didn't like the architecture I grew in an adhoc way". But equally, there are many out there that ARE happy with what they grew. So that's the decision.
well my use-case is pretty complicated. a data entry wizard. i can imagine having to deal with many things myself, routing, state-ful complex ui widgets
My guess is that re-frame will be useful
our current implementation is in angular 1. it is a nasty spaghetti-woven state machine
Yeah, okay, I'm convinced. You need re-frame. It is more overhead to get going. Sorry about that. But your future self will thank you.
i have a feeling that have a model for handling state changes is going to be very helpful
re-frame constrains you, but pays you back with regularity. BTW, this is new. Might help: https://github.com/kishanov/re-frame-datatable https://kishanov.github.io/re-frame-datatable-example/
@notanon coming from Angular 1, my guess is that you are going to be shocked by the simplicity you are about to experience. :-)
Doesn't mean there isn't a learning curve
I can remember my impotent fury at CLJS early on, as I struggled with not being able to mutate things
How THE HELL can this do anything useful, I raged.
Good luck
Regarding Reagent, be sure to read the Tutorials at the bottom of this page: https://github.com/Day8/re-frame/wiki#reagent-tutorials
Early