Mobx spike

[grod220]

Closes https://github.com/penumbra-zone/dex-explorer/issues/66 Closes https://github.com/penumbra-zone/dex-explorer/issues/67

Takes over from: https://github.com/penumbra-zone/dex-explorer/pull/70

An experiment of using Mobx for the connection + streaming status state. Observations:

Pros

• No need for selectors/useShallow anymore. Just import what you need. Optimizations built in.
• Classes where you can mutate variables feel like the better syntax versus an immutable object w/ function fields
• Feels like less boilerplate (?). Interfaces do not need to be defined and class types are inferred.
• Effects built in w/ when() and don't need to enter react context to form store relationships + reactions

Cons

• Remembering to wrap components with HOC observer() if relying upon observable vars
• Actions often must be indicated. Sometimes can be inferred with makeAutoObservable(), but often have to make explicit setter functions. Adding decorator syntax could help with this.

[TalDerei]

from my perspective, using Mobx for managing client-side app state seems to be exactly what we're looking for in a HFT DEX UI since it focuses on fine-grained reactivity, keeping the UI reactive with a performant batch update system while intelligently avoiding unnecessary re-renders.