How we do Vue: one year later (2017)
about.gitlab.com
How we do Vue: one year later (2017)
1–10 of 159 posts
Re: How we do Vue: one year later (2017)
#2Re: How we do Vue: one year later (2017)
#3Re: How we do Vue: one year later (2017)
#4That's the problem with large-scale Vue apps. Vue is awesome until you need to use VueX, after which it just becomes an inferior version of React + Redux.
Re: How we do Vue: one year later (2017)
#5> Just use VueX That's the problem with large-scale Vue apps. Vue is awesome until you need to use VueX, after which it just becomes an inferior version of React + Redux.
Re: How we do Vue: one year later (2017)
#6> Just use VueX That's the problem with large-scale Vue apps. Vue is awesome until you need to use VueX, after which it just becomes an inferior version of React + Redux.
Re: How we do Vue: one year later (2017)
#7Re: How we do Vue: one year later (2017)
#8Might wanna add a [2017] tag in the title.
Re: How we do Vue: one year later (2017)
#9Re: How we do Vue: one year later (2017)
#10> Just use VueX That's the problem with large-scale Vue apps. Vue is awesome until you need to use VueX, after which it just becomes an inferior version of React + Redux.
I found Redux to be highly over-engineered in contrast to Vuex which is a lot like MobX - easy to use, yet powerful.