Re:How we do Vue: one year later (2017)
by wishinghand on Monday March 18, 2019 @06:50PM
(#19426153)
I've always found Redux to be an overcomplicated mess, whereas Vuex is quite simple and has a nice, logical flow. For those who think it's still too complex, I've heard that Pathify https://davestewart.github.io/vuex-pathify is a great solution.
I regret every line of Redux boilerplate I ever wrote before discovering MobX. MobX is now even more fantastic with the new proxy based implementation.
Reading up on VueX.. Not really looking forward to having to use it over MobX.
VueX is terrible. I'm using vue with MobX, and though it's not as seamless as with react, you still get most of the benefits. There's just nothing that comes close to it.
> MobX is now even more fantastic with the new proxy based implementation.
What does this mean? I've used MobX in the past but curious what has changed with this.
Re:How we do Vue: one year later (2017)
by wishinghand on Tuesday March 19, 2019 @12:19PM
(#19432276)
I'm wondering if it's this: https://davidwalsh.name/javascript-proxy
Inferior? How exactly?
I found Redux to be highly over-engineered in contrast to Vuex which is a lot like MobX - easy to use, yet powerful.
> highly over-engineered
Redux is a couple hundred lines of code. A good way to learn the pattern it to reimplement it yourself - which you could probably do in ~100LOC if you ignore the helper functions
I believe the OP meant in the sense of say, implementing a client for a network service in python using recursion with multiple re-entry points instead of a for loop..
Re:How we do Vue: one year later (2017)
by enraged_camel on Monday March 18, 2019 @08:54PM
(#19427033)
>>Redux is a couple hundred lines of code.
That's not a refutation of the parent's statement.
Re:How we do Vue: one year later (2017)
by nerdwaller on Monday March 18, 2019 @06:25PM
(#19425981)
This is my thought as well, adding that it feels like way less boilerplate due to the integration with the underlying framework
I like the idea that the 200 line event dispatching state atom is more over-engineered than a framework that works off wrapped "observable" objects and uses ES6 proxy magic (MobX). Do proxies work in IE11? Didn't think you could just polyfill them.
Agreed. Give me MobX over Redux any day of the week.
Re:How we do Vue: one year later (2017)
by pietrovismara on Monday March 18, 2019 @06:08PM
(#19425850)
Ever tried vuex-module-decorators? Add that to the recipe and using vuex with Typescript becomes really easy and a pleasure to write.
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.