States can also be organized in some central places (aka. stores). You can use Tini Store (very simple, ~50 lines) or other state management solutions such as MobX, TinyX, ... - Source: dev.to / about 1 year ago

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid,... - Source: dev.to / about 1 year ago

Mutable-based: leverages proxy to create mutable data sources which can be directly written to or reactively read from. Candidates in this group are MobX and Valtio. - Source: dev.to / over 1 year ago

Looks good! FWIW I always felt the observable pattern much more intuitive than the redux/reducer style. Something like https://mobx.js.org/ Things get hairy in both, but redux pattern feels so ridiculously ceremonially to effectively manage a huge global state object with a false sense of "purity". Observables otoh say "fuck it, I'm mutating everything, do what you want with it". - Source: Hacker News / over 1 year ago

It's important to note that Redux is just one of many options for global state management in a React application. Other popular options include MobX and the React context API.context API](https://reactjs.org/docs/context.html). - Source: dev.to / over 2 years ago

It would be awesome to develop something abstract and useful for usage as common PL (besides just solving specific problem), but it's really hard to develop a general purpose language (with memory management, mutations, etc.). For example, at my work I built reactive library mostly similar to Rx.js or Bacon.js, but with additional ability to compose different reactive systems on top of each other, so that... Source: over 3 years ago