React's state management is so cumbersome (including redux). I am making an open source state management (for React, Angular, Vue) that will be as easy as possible for newbies (and includes cool stuff like very simple observables for others). Follow me on twitter if you want to know about that in a month (or two) twitter.com/not_borats_code
Seems like MirrorJS while having good intentions and is overall a good thing, sacrifices features to simplicity (quote from their readme: "define routes without caring about history"). Also if it does not have compatibility with react, I doubt it has a bright future.
P.S. I've looked at your profile, if you have .NET background, you might want to look to angular instead of react. The former is a more solid base for new, big-scaled project, the latter is good for small to medium projects, or for existing projects with legacy (in any language).
Vue is also good, but it is in the same basket with React, unlike Angular. By compatibility I meant the same API. If MirrorJS does not compatible with React, all the libraries and entire ecosystem for React is useless for MirrorJS. I just didn't look if it's compatible, so I don't know if it's true.
React's state management is so cumbersome (including redux). I am making an open source state management (for React, Angular, Vue) that will be as easy as possible for newbies (and includes cool stuff like very simple observables for others). Follow me on twitter if you want to know about that in a month (or two) twitter.com/not_borats_code
I've started using MirrorJS, and I found it to be quite easy to get started with.
MirrorJS looks like something one with an extensive experience with Redux. Kind of like how I might end up organizing redux code.
Seems like MirrorJS while having good intentions and is overall a good thing, sacrifices features to simplicity (quote from their readme: "define routes without caring about
history
"). Also if it does not have compatibility with react, I doubt it has a bright future.P.S. I've looked at your profile, if you have .NET background, you might want to look to angular instead of react. The former is a more solid base for new, big-scaled project, the latter is good for small to medium projects, or for existing projects with legacy (in any language).
Thanks Nurbol for the tip on Angular. I will consider it over Vue for the next framework.
Might ask what you meant by the compatibility issue?
Vue is also good, but it is in the same basket with React, unlike Angular. By compatibility I meant the same API. If MirrorJS does not compatible with React, all the libraries and entire ecosystem for React is useless for MirrorJS. I just didn't look if it's compatible, so I don't know if it's true.
I see that MirrorJS has a devdependency on
"react": "^16.3.2"
, so if React v.17 is release it'd not be compatible.