MobX VS Bacon

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, Starbeam, Svelte, Vue, Wiz, and more…

MobX

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.

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".

MobX Documentation

There's also others libraries like https://github.com/mobxjs/mobx which aren't specific to RN but can be used in any JS environment.

Valtio is like simplified MobX

Link: https://mobx.js.org

But I want to impress upon you that this is just only one of many patterns you can use this hook for. While this is subjective, I am personally not a huge fan of Redux and this type of pattern. It has its merits, but I think once you want to start layering in new patterns for actions, Mobx, Zustand, or XState are preferable in my personal opinion.

bacon.js

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 streams declaration order won't matter and might be deployed separately while being glued at run-time (as long as stream names match). It's all cool, but system would only allow reactive functions (without imperativity and mutable objects), then the whole code would look really ugly and I definitely wouldn't be able to promote it among my colleges ^^, especially regarding how hard people migrate to new paradigms - sorry for complaining 😊.

Reactor is based on the same reactive principles as Bacon.js and Knockout.js.

Bacon.js - Functional reactive programming.

I remember hearing about Bacon.js one day and checking out their Getting Started page. In it, they demonstrate a counter using the Bacon event streaming library. This is the demo code: