undefined | Better HN

0 pointssatvikpendem3y ago0 comments

When you have a big app, it becomes a spaghetti mess, and I speak from personal experience having to untangle that spaghetti.

0 comments

spion3y ago

Counterpoint: I've worked on a big application that used MobX and had no such issues.

LAC-Tech3y ago

What approach do you prefer for big apps?

The state has to go somewhere, curious how you choose to handle it.

satvikpendemOP3y ago

Personally I just use Redux Toolkit with RTK Query for any synchronization with backend state. What I like about Redux is that it takes the immutable functional approach, you cannot change previous state but must instead derive new state from the old state very explicitly. In this way, it's the antithesis of signal-based state.

dmitriid3y ago

> What I like about Redux is that it takes the immutable functional approach

Strange that you don't like spaghetti, but then praise Redux that is spaghetti exemplified: dozens of functions, and wrappers, and hooks eerywhere. Trying to trace how a value gets changed through the three-four layers of wrappers is like pulling teeth through the anus.

And looking at the current reincarnation of this abomination, it is marginally less spaghetti, and converging on the same signals code that everyone is converging on.

1 more reply

j / k navigate · click thread line to collapse