Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison with proxy-state-tree #45

Closed
joelmoss opened this issue Mar 28, 2020 · 2 comments
Closed

Comparison with proxy-state-tree #45

joelmoss opened this issue Mar 28, 2020 · 2 comments

Comments

@joelmoss
Copy link

I came across overmind the other day, and their proxy-state-tree library that seems to do the same thing as useTrackedState() does.

So I was wandering if you were familiar with it, and how it compares.

thx 馃憤

@dai-shi
Copy link
Owner

dai-shi commented Mar 28, 2020

Hi,
I know roughly how proxy-state-tree works. There was a bit of discussion while developing reactive-react-redux in early days.

Basically, it's similar. There's a big difference in design choices. MobX and proxy-state-tree are based on mutable objects, where as react-tracked and reactive-react-redux are based on immutable objects. Does it make sense?

In general, mutable object approach can be a little bit faster because we can reuse Proxies. Immutable object approach is better to support Concurrent Mode, I believe.

For your information, I already split the tracking library to proxy-compare (whose README notes similar libraries), and react-tracked v2 depends on it. #43

@dai-shi
Copy link
Owner

dai-shi commented Dec 2, 2020

Closing as resolved.

@dai-shi dai-shi closed this as completed Dec 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants