[badthingfactory]

You have a root component. Run the interval within that component where you have access to state.

[bendavis381]

That's essentially redux: root state.

[badthingfactory]

If that was "essentially redux", redux would have no reason for existence.

[RussianCow]

Except for the fact that it drastically lowers the amount of manual props passing you have to do, and allows you to achieve much better separation of concerns. It is essentially Redux, only much worse the more complex your app is.

[badthingfactory]

> It is essentially Redux, only much worse the more complex your app is.

so... not at all like Redux then. C# is essentially Python except it has different syntax and static typing.

[RussianCow]

The entire Redux library is something like 300 lines of code, most of which is sanity checks. It is basically the same thing as having one root component handle all your state, it just adds a tiny bit of magic for convenience. If you're comparing that to using a completely different language, I encourage you to learn more about how Redux actually works, because it's really very simple.

[eropple]

It literally IS having a root component manage state. That's what the Provider class does (enables connect() to populate via a Redux store in context).

[badthingfactory]

I understand Redux, have used it many times and have read the source code. I don't understand the argument that it is "basically is the same thing as having a root component handle all your state".

It's that plus actions, reducers, dispatcher, middleware, and HoCs for connecting components to global state. So it's not basically the same thing at all.

[Kiro]

And if it's in a module outside the component tree?

[k__]

As I said, my approach isn't a one size fits all.

At the moment I do React-Native projects, where every app is self contained. On the Web you often have more mashup.

But the approach still works for most Web UIs too, just not for all.