How we do Vue: one year later (2017)

Re:How we do Vue: one year later (2017) by Tade0 on Monday March 18, 2019 @06:18PM (#19425934)

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.

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by wp381640 on Monday March 18, 2019 @08:04PM (#19426661)

> 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

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by Rapzid on Monday March 18, 2019 @11:02PM (#19427720)

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..

[ Parent | on HN ]

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.

[ Parent | on HN ]

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

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by Stoids on Tuesday March 19, 2019 @12:41PM (#19432525)

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.

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by jmull3n on Tuesday March 19, 2019 @03:17AM (#19428744)

Agreed. Give me MobX over Redux any day of the week.

[ Parent | on HN ]