Open solkimicreb opened 5 years ago
Asc2011
commented
5 years ago Hi solkimicreb,
big thx for publishing easy-state. I started exploring easy-state with react-native last week. I like it very much. Right now i'm looking at Reactotron and
avierr
commented
5 years ago What is your project's name? If it is a work/open-source project please add a company name/link too. The project is around having a UI for device Management/emulation. Company: (Cannot Disclose).
What is your project's size (LOC or number of people working on it)? basically over 1M lines of backend.
Is it okay if I use the project's name and logo in a future article or the readme? (I won't be offended by a no.) Yes please message me and I 'll try and get these things sorted.
Is there anything you miss from easy-state or anything you find a bit annoying? More Documentation on Typescript would be nice.
haench
commented
5 years ago Hi,
I am pretty new to react and front end development overall. My first project uses react-easy-state. Maybe you want to have a look:
https://github.com/haench/haenchs-planner
https://haench.github.io/haenchs-planner/
(Not mobile friendly)
Fell free to reference it if you feel like. Also I am happy to receive criticism as I just did what felt right to me, but I have basically no experience.
evnix
commented
5 years ago We use it heavily in Codoforum, A Forum Software (Website: https://codoforum.com) and we are porting another software to use react-easy-state instead of redux. It saves us a huge amount of boilerplate when compared to redux.
Filodoxia
commented
5 years ago I'm working as student assistant and am maintaining and developing a little tool to automatically visualize organization and process structures in Microsoft Visio. Data input and storage is handled via an Access DB and forms. Always wanted to do some web development and thought it could be nice to migrate the project to a web app and might even base my master thesis on it (I'm studying Information Systems). Looked into Redux but easy state seemed simpler for the beginning since you really only have stores and views which I really like. Got a basic setup running but when I wanted to migrate to using create-react-app I ran into an error described in #21 but couldn't solve it yet. See #82 for the issue I opened for this.
luisherranz
commented
5 years ago We are using a fork of react-easy-state and observer-util in Frontity, a new framework to create React themes for WordPress :)
It's a fork instead of the original libraries because we needed to do some modifications to fit our architecture and I'd like to state that it is one of the most brilliant codebases I have found in my career. Really simple, understandable, well thought and performant.
Kudos to @solkimicreb for his great work!
What is your project's size (LOC or number of people working on it)?
I have no idea, but kind of big and growing every day :) https://github.com/frontity/frontity
Is it okay if I use the project's name and logo in a future article or the readme? (I won't be offended by a no.)
Absolutely.
Is there anything you miss from easy-state or anything you find a bit annoying?
We did a fork because we need to add middleware for devtools and state filtering. But that's not something I consider either observer-util or react-easy-state should have so it's ok as it is.
pvider
commented
5 years ago @solkimicreb, I am software architect from Russian company where we are working on taskrabbit-like service both web and native and I am planning to use your amazing state manager. Keep up your excellent work! Right now I am testing my own mobx-state-router fork powered by react-easy-state. Originally it is very powerful router which I use for web and native via mobX, kudos to @nareshbhatia.
Some statisitcs. We have 280KB of global store code and it is fully shared between react-web and react-native. Webapp is 880KB of local state and view (without global store). Native is in development (half-finished) so it is only 370KB of local state and view (without global store). Server is 840KB of code. Middle size of a line is about 50 bytes in our case. So total LoC is roughly 48K.
Right now we are using mobX however I want easy-state-tree because: 1) I am tired of @observable, @action, runInAction, inject, etc. everywhere. While react-easy-state just works. 2) mobX as I know doesn't work well with hot reloading, and our class-based stores make it even worse. While with react-easy-state I simply import my proxy-objects into files without any class inits and separate them into actions and initial state. 3) I am not fully sure about it but I think mobx is harder to debug. Maybe it is because mobx v4 (without proxies) but I had some incompatibilities of mobX and antd. I like react-easy-state simplicity here.
After migration from mobX stores I will write more info about us here, I hope it will go smoothly and soon I will :)
jpiepkow
commented
5 years ago Use react-easy-state at AppDoctor.
Yes you can use the name/logo in readme.
I would say react-easy-state worked exactly as expected. I have some issues with using it with the new react-native hooks release but I will open a separate issue on that.
zachariahtimothy
commented
4 years ago Using it on 2 projects now;
CurtiWeather
USDA APHIS
Hi everyone!
Thanks to all of you, easy-state usage is nicely growing and I feel like it's time for this issue 🙂Please answer the following questions if you use easy-state:
Thanks!