Interesting article. Pondering if some of my struggles have been around that 
issue, but not sure off the top of my head.

I've definitely used Reagent's create-class on a couple of complex components. 

Jamie

On May 14, 2015, at 5:01 PM, Marc Fawzi <[email protected]> wrote:

> Reagent's create class allows normal React lifecycle callbacks without any 
> verboseness. 
> 
> However, the big surprise for me was finding out that both Reagent and Om use 
> async updates for everything when React has problems with it in some cases, 
> like controlled inputs. 
> 
> http://jonase.github.io/nil-recur/posts/14-12-2014-controlled-input.html
> 
> Dan Homlsand (Reagent's author) is looking into it, so we'll see what he'll 
> come back with. I might be naive here but I'm hoping that we can use async 
> setState for all updates except for controlled inputs.
> 
> 
> Sent from my iPhone
> 
> On May 14, 2015, at 1:20 PM, Jamie Orchard-Hays <[email protected]> wrote:
> 
>> No kidding. I have this long blog post germinating in my head about my 
>> experiences with Om and re-frame now that I've developed a reasonably-sized 
>> app in each. Problem is, I have no time to write it. One thing I've come to 
>> appreciate about Om over Reagent is that despite it being more verbose, it's 
>> always clear where you are WRT the React lifecycle and state. Reagent, being 
>> less formal, lends itself to some confusion over what's happening where.
>> 
>> In general, I agree with some comments I've seen in this group recently that 
>> we really have a long way to go with rich client web apps. It's still way 
>> too time-consuming, painful and not formalized enough, even with the awesome 
>> tools we have around already. Simple *and* easy is the brass ring.
>> 
>> 
>> On May 14, 2015, at 3:35 PM, Colin Yates <[email protected]> wrote:
>> 
>>> +1 I keep thinking "yeah, this is the stack I will use, let's invest in 
>>> this" then something new comes along. Not good for those of use affected 
>>> with "grassisalwaysgreeneritus" :).
>>> 
>>> On 14 May 2015 19:39, "Jamie Orchard-Hays" <[email protected]> wrote:
>>> This is really interesting stuff. I'd looked over Hoplon a year ago and 
>>> didn't use it as it wasn't React-based. I really liked the 
>>> spread-sheet/cell metaphor. I wish I had more time to explore all of these 
>>> libs! :) CLJS is enjoying quite a Cambrian explosion of interesting 
>>> libraries.
>>> 
>>> Jamie
>>> 
>>> On May 14, 2015, at 2:26 PM, Ruslan Prokopchuk <[email protected]> wrote:
>>> 
>>> > Jamie, exactly, I took re-frame (it's awesome!) and replaced 
>>> > subscriptions mechanism with Javelin cells. I like Javelin, it allows 
>>> > elegant and succinct data coordination. See todomvc example in the amper 
>>> > and re-frame repos for comparison.
>>> >
>>> > Also I've replaced Reagent with Om because of my internal needs, but 
>>> > re-frame architecture is View-agnostic in its heart, and I've implemented 
>>> > it in ampere. Now it includes only Om adapter, but more to come with 
>>> > examples (I plan to make todomvc views.cljs port for every supported View 
>>> > library). Hoplon does not require any adapter at all, for example ;-)
>>> >
>>> > --
>>> > Note that posts from new members are moderated - please be patient with 
>>> > your first post.
>>> > ---
>>> > You received this message because you are subscribed to the Google Groups 
>>> > "ClojureScript" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send an 
>>> > email to [email protected].
>>> > To post to this group, send email to [email protected].
>>> > Visit this group at http://groups.google.com/group/clojurescript.
>>> 
>>> --
>>> Note that posts from new members are moderated - please be patient with 
>>> your first post.
>>> ---
>>> You received this message because you are subscribed to the Google Groups 
>>> "ClojureScript" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/clojurescript.
>>> 
>>> -- 
>>> Note that posts from new members are moderated - please be patient with 
>>> your first post.
>>> --- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "ClojureScript" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/clojurescript.
>> 
>> 
>> -- 
>> Note that posts from new members are moderated - please be patient with your 
>> first post.
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "ClojureScript" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/clojurescript.
> 
> 
> -- 
> Note that posts from new members are moderated - please be patient with your 
> first post.
> --- 
> You received this message because you are subscribed to the Google Groups 
> "ClojureScript" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/clojurescript.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.

Reply via email to