Live data from Hacker News

Vue.js: the good, the meh, and the ugly

medium.com

381–382 of 382 posts

Re: Vue.js: the good, the meh, and the ugly

#381

My problem with current gen frameworks is composition and modularity with components. Making components stateless and having all data come in as props from parents is good for modularity but how do you pass data back to the parent? This is where the modularity becomes awkward. I know of two ways in vue to do this and both ways either completely break or make modularity awkward. The first way is to signal the parent w…

Creating a bus with a new vue object might be what you're looking for if vuex is truly too much boilerplate. You can also implement v-model, but I don't think that's what you're looking for.

It's not boilerplate that's my problem. It's modularity and composition. Components do not have it. A bus ties a component to a bus rather than a vuex global.

Re: Vue.js: the good, the meh, and the ugly

#382

Earlier quoted context omitted.

You wrote "React take the strongest stance" but you meant redux right?

No, React has a notion of a single giant state object, right?

No. Vanilla React just give you the option to store state of any size in any component.
Post reply on HN