Vlad Balin
Vlad Balin
With that change, we will receive the solid _core annotation_ subset working for both props and state. Annotation level 1 - just assertions. Works for everything. `Type`, `Type.isRequired`, `Type.has.check` Level...
That's really bad.
At the first glance, it looks like it makes the custom state management impossible.
1) State must be initialized before the render in the constructor. The lack of the destructor in new React will cause memory leaks in some cases unless the new Events...
Nah, it's even worse. In case of the WeakMap _keys_ are weak and there's no iteration support. Thus, there seems to be no obvious way to use it as an...
> I have noticed that its problematic for fresh programmers to use setState in some components and state.xx = in others. Well. That can be solved rather easily. Look at...
> Also we are only using listenToProps so the lib is overkill. I did some measurments for the initializing of a component with pure react (0.1ms) and MVx (5.0ms). With...
> Also we are only using listenToProps so the lib is overkill. I did some measurements for the initializing of a component with pure react (0.1ms) and MVx (5.0ms). That's...
So, React-MVx is written to support that architectural approach I briefly described above. If you prefer to go with mobx style (singletons + local events subscription), you don't really need...
But I don't like mobx style. It's memory hungry, too magical thus it's easy to make a mistake, and there are no real-world performance problems which can justify that as...