Vue 3.0 Updates [slides]

Post by orangecat » Sat, Nov 17, 2018, 5:14 PM UTC

williamdclt wrote: post #62

k__ wrote: post #45

Earlier quoted context omitted.

I think two-way-binding is the reason why many people prefer Vue to React. If you did Ember or Angular1, Vue is much easier to grasp.

Well, one-way binding (or rather, unilateral data flow) is why I prefer React :)

Post by williamdclt » Sat, Nov 17, 2018, 5:54 PM UTC

orangecat wrote: post #81

williamdclt wrote: post #62

Earlier quoted context omitted.

Well, one-way binding (or rather, unilateral data flow) is why I prefer React :)

"v-model" isn't two-way binding like in AngularJS where both parent and child can modify the same data. It's just shorthand for defining a property and an event handler. Like in React, properties flow down and events flow up. See https://vuejs.org/v2/guide/forms.html

Post by petilon » Sat, Nov 17, 2018, 6:06 PM UTC

TekMol wrote: post #16

My feeling is that most people who use Vue or React only need a template engine. Typical use case: You have an array of objects and a template how each object should look like. So you do... {{ user.name }} let userList = new Vue({ el : '#users', data: { users: users } }) ...to make Vue render the list of objects. This is the only thing I ever use these frameworks for. Everything else I think I can implement in a bett…

Post by pier25 » Sat, Nov 17, 2018, 6:15 PM UTC

TekMol wrote: post #16

My feeling is that most people who use Vue or React only need a template engine. Typical use case: You have an array of objects and a template how each object should look like. So you do... {{ user.name }} let userList = new Vue({ el : '#users', data: { users: users } }) ...to make Vue render the list of objects. This is the only thing I ever use these frameworks for. Everything else I think I can implement in a bett…

Post by gbuk2013 » Sat, Nov 17, 2018, 7:28 PM UTC

TekMol wrote: post #77

gbuk2013 wrote: post #51

Earlier quoted context omitted.

One should use what is necessary and no more. If server side templates work for you - great. My rule of thumb: if I need to do more then a trivial amount of DOM manipulation then I will use a framework, because otherwise I will end up writing my own anyway (which I can easily do) which wastes development time. For projects with several developers a framework can help maintain common coding style and reduce ramp up ti…

Could you add the lines needed to the above example to make the user list grow / shrink real time via websockets? Would be interested to see how you would implement that.

    mounted () {
      this.$socket.subscribe(‘stuff’, data => {
        this.$store.commit(‘update_stuff’, data);
      });

    computed () {
      stuff () {
        return this.$store.state.stuff;
      }
    }