Skip to content
This repository has been archived by the owner on Feb 17, 2022. It is now read-only.

Why movue #8

Open
nighca opened this issue Aug 14, 2017 · 2 comments
Open

Why movue #8

nighca opened this issue Aug 14, 2017 · 2 comments
Labels

Comments

@nighca
Copy link
Owner

nighca commented Aug 14, 2017

Why MobX + movue, instead of Vuex?

  1. MobX provides more flexible and powerful observable system (shallow, ref, map...)
  2. You may not like Vuex (action & mutation, the way to compose...)
  3. We want store-realization irrelevant to view-realization (possibility to switch among different view libraries without rewriting store)
@nighca nighca changed the title why movue Why movue Oct 25, 2017
@sushruth
Copy link

I have been trying to really convince myself about the action and mutation agenda. But I am not able to buy that. I am sure there are a few developers like me. Thanks for your effort!

@ozzioma
Copy link

ozzioma commented Aug 30, 2020

Agreed and thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants