status-im/re-frame
2
0
Fork 0
mirror of https://github.com/status-im/re-frame.git synced 2025-02-23 07:18:22 +00:00
Code Issues Projects Releases Wiki Activity

whitespace

Browse Source
This commit is contained in:
Mike Thompson 2017-10-21 16:19:56 +11:00
parent ba02f10972
commit cc7bbb7d30
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/FAQs/DoINeedReFrame.md
View File

@ -12,7 +12,7 @@ But it only supplies the V part of the traditional MVC triad. When
your application gets bigger and more complicated, you'll need to
find solutions to questions in the M and C realms. Questions like "where do I put control logic?".
And, "how do I manage state?". And, "How do I put up a spinner
when waiting for CPU intensive computations to run, while allowing the user to press Cancel?"
when waiting for CPU intensive computations to run, while allowing the user to press Cancel?"
How do I ensure efficient view updates? How do I write my control logic in a way that's testable?
How should new websocket packets be communicated with the broader app? Or GET failures?
@ -36,9 +36,9 @@ Now, in response, some will enthusiastically say "yes, I want to grow my own
architecture. I like mine!". Fair enough - its a fun ride!
I think problems arise when this process is not conscious and purposeful. You
can accelerate quickly with Reagent and get a bunch of enjoyable early wins, but then
ultimately end up off the road, in the paddock, because of
one of the corners leading up to a bigger application.
can accelerate quickly with Reagent and get a bunch of enjoyable early wins, but then
ultimately end up off the road, in the paddock, because of the twists and turns
leading up to a bigger application.
I've had many people (20?) privately say to me that's what happened to them. The real
number would obviously be much higher. And that's pretty much the reason for