monocle-ts VS zustand

You may be interested also in checking out the implementation of Lens in monocle-ts, one of the libraries in the fp-ts ecosystem

For anyone - anyone who's faffed around with JavaScript's spread syntax when working with nested immutable data, anyway - struggling to understand the general concept or utility of lenses, I'd encourage looking into monocle-ts. The motivation [0] that kicks off the README instantly made me a believer, and TypeScript's idiosyncratic type system makes using the library remarkably natural; it fits right in without needing to deal with anything analogous to Template Haskell.

[0] https://github.com/gcanti/monocle-ts#motivation

You could have a look at the monocle-ts library. It was designed to deal with this kind of problem.

spectacles-ts integrates seamlessly with the fp-ts ecosystem (it's built on top of the excellent monocle-ts library)

lenses help with this quite a bit, check out monocle-ts

Zustand is a lightweight state management library that embraces a more decentralized approach compared to Redux. It provides a simple API for managing state as isolated stores, making it easier to work with and reducing boilerplate code.

The accounts manager is responsible for storing and managing all the accounts that users have used on your app. You can use any state management solution such as Redux, Zustand, Jotai, React Context etc.

This excellent state manager removed even more of Redux's boilerplate at the cost of some debugging power. You can think of Zustand like a very simplistic RTK that scales down way better and scales up only a little worse.

For global state, Zustand or RTK

zustand is really good and easy to learn. I don't use redux anymore.

Zustand is like simplified Redux

Redux is also not ideal to start with. It has great features, but can be difficult to learn at first. Zustand is a simpler library that has many similar concepts. I'd recommend it as a starting point before learning Redux.

Redux seems to mostly be used at large companies that already have Redux deeply embedded in their stack. I would not recommend learning Redux in 2023. I don't think it's the future. Context API is all you need for most projects. At my company we don't even use Context API (where possible). We just use zustand! https://zustand-demo.pmnd.rs/

I feel like zustand internal still use hooks at some point: https://github.com/pmndrs/zustand/blob/main/src/context.ts