(new) context API can solve issues with components in totally different places

Will have to look into that one some day.

Or maybe not. UI is annoying at any level. 😄

x)

Nah, redux is ok. Storing form state in redux is not.

The new Context API would probably be better if you want to locally share state.

Or just local state in a Form component

For a form, indeed

I mean I think redux has pretty large benefits. It enforces a fuctional approach (besides ultimately the state mutation and side effect, but at least those are controlled). The single state tree makes everything predictable and allows things like easy time travel debugging by making everything a declarative action.

Obviously there are times where you want "local state" that definitely shouldn't be in redux.

The pattern behind redux is great, it just doesn't have to be applied to the whole application state

it should not be

But I still believe data should be decoupled from the view / view logic.

nobody argued against that ^^

That's also why hooks are useful.

In my first link above (dan's article on medium) there is an example of redux-style logic in a "normal" component

You can make custom hooks and reuse them across components.

hooks break referential transparency

it's trendy in the JS community to slap functional programming stickers onto everything, but if you can't get the basics right, something is broken ^^

Well I still think redux is a lot better than the approach MobX and Coconut takes with "observables".

To me it adds unnecessary complexity, and starts looking like inheritance again.

I see you're super informed on the subject ^^

Not a big fan of observables too but to be fair maybe it's just because I still haven't given them either a try or a proper look

FYI inheritance is disallowed on coconut models ;)

Yeah, to be fair I've never tried Coconut, but had a very bad experience with MobX.

Which at least on the surface it looked similar to, but again never did a deep dive.

what was the main pain point?

I just felt like it added unnecessary complexity, I don't see the point of observables, I think things felt circular when I tried to use it.

For example when someone asked about combining two state objects in an issue, they said they don't enforce anything like that, and you can encapsulate logic inside those state objects to grab data from another state object.

To me that's just like wtf.