mirror of
https://github.com/status-im/re-frame.git
synced 2025-02-23 07:18:22 +00:00
We're now officially in the Post FAQ era. But this is one more tweak.
This commit is contained in:
parent
5f238f1d28
commit
4f028e1387
@ -2,8 +2,7 @@
|
|||||||
|
|
||||||
#### New Features
|
#### New Features
|
||||||
|
|
||||||
- added [a new FAQ entry](/docs/FAQs/DoINeedReFrame.md) Why not just Reagent?
|
- added [a new FAQ entry](/docs/FAQs/DoINeedReFrame.md) Reagent looks terrific. Why do I need re-frame?
|
||||||
|
|
||||||
|
|
||||||
## 0.10.2 (2017.10.07)
|
## 0.10.2 (2017.10.07)
|
||||||
|
|
||||||
|
@ -8,16 +8,17 @@ conceptual overhead for not much benefit!
|
|||||||
First, I agree, Reagent is terrific. If your application is small and simple,
|
First, I agree, Reagent is terrific. If your application is small and simple,
|
||||||
then standalone Reagent is absolutely a fine choice.
|
then standalone Reagent is absolutely a fine choice.
|
||||||
|
|
||||||
But it does only supply the V part of the traditional MVC triad. As a result, when
|
But it only supplyiesthe V part of the traditional MVC triad. When
|
||||||
your application starts to get bigger and more complicated, you will need to
|
your application gets bigger and more complicated, you'll need to
|
||||||
find solutions to questions in the M and C realms. Questions like "where does the control logic go?".
|
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, coordination issues like "How do I put up a spinner
|
And, "how do I manage state?". And, "How do I put up a spinner
|
||||||
when waiting for the database, and take it down correctly?". How do I ensure
|
when waiting for CPU consuming computations to run?" How do I ensure
|
||||||
efficient view updates? How do I write my control logic in a way that's testable?
|
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?
|
How should new websocket packets be communicated with the broader app? Or GET failures?
|
||||||
|
|
||||||
These questions accumulate. Reagent, by itself,
|
These questions accumulate.
|
||||||
provides little guidance and, so, you'll need to
|
|
||||||
|
Reagent, by itself, provides little guidance and, so, you'll need to
|
||||||
come up with your own solutions. The choices you make will accumulate too and,
|
come up with your own solutions. The choices you make will accumulate too and,
|
||||||
over time, will become baked into your code base,
|
over time, will become baked into your code base,
|
||||||
becoming increasingly difficult to revisit.
|
becoming increasingly difficult to revisit.
|
||||||
@ -34,10 +35,10 @@ various questions you'll face when developing your app.
|
|||||||
Now, in response, some will enthusiastically say "yes, I want to grow my own
|
Now, in response, some will enthusiastically say "yes, I want to grow my own
|
||||||
architecture. I like mine!". Fair enough - its a fun ride!
|
architecture. I like mine!". Fair enough - its a fun ride!
|
||||||
|
|
||||||
I think the only danger arises if this process is not conscious and purposeful - if
|
I think problems only arise when this process is not conscious and purposeful. You
|
||||||
someone gets going quickly with Reagent and has a bunch of enjoyable early wins, but
|
can accelerate quickly with Reagent and get a bunch of enjoyable early wins, but then
|
||||||
ultimately ends up in the weeds because they didn't understand the road they were driving as
|
ultimately end up off the road, in the paddock, because of
|
||||||
their application got bigger.
|
one of the corners leading up to a bigger application.
|
||||||
|
|
||||||
I've had many people (20?) privately say to me that's what happened to them. The real
|
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
|
number would obviously be much higher. And that's pretty much the reason for
|
||||||
@ -46,7 +47,7 @@ this FAQ - this happens a bit too often.
|
|||||||
So, my advice is ... if your application is a little more complicated,
|
So, my advice is ... if your application is a little more complicated,
|
||||||
be sure to make a conscious choice around architecture. Don't think
|
be sure to make a conscious choice around architecture. Don't think
|
||||||
"Reagent is all I need", because one way or
|
"Reagent is all I need", because one way or
|
||||||
another you'll be using Reagent + a broader architecture.
|
another you'll be using "Reagent + a broader architecture".
|
||||||
|
|
||||||
### Some Choices Made By re-frame
|
### Some Choices Made By re-frame
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
## Frequently Asked Questions
|
## Frequently Asked Questions
|
||||||
|
|
||||||
1. [How can I Inspect app-db?](Inspecting-app-db.md)
|
1. [How can I Inspect app-db?](Inspecting-app-db.md)
|
||||||
2. [Why not just Reagent?](DoINeedReFrame.md)
|
2. [Reagent looks terrific. Why do I need re-frame?](DoINeedReFrame.md)
|
||||||
2. [How do I do full-stack re-frame?](FullStackReframe.md)
|
2. [How do I do full-stack re-frame?](FullStackReframe.md)
|
||||||
2. [How long after I do a dispatch does the event get handled?](When-Does-Dispatch-Happen.md)
|
2. [How long after I do a dispatch does the event get handled?](When-Does-Dispatch-Happen.md)
|
||||||
2. [How can I use a subscription in an Event Handler](UseASubscriptionInAnEventHandler.md)
|
2. [How can I use a subscription in an Event Handler](UseASubscriptionInAnEventHandler.md)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user