My 5 cent after 5 minutes: no rendering for incomplete models?

This post is from someone who spent 5 minutes with the framework, while using Angular.JS for every day work…

The very first (Hello World!) example takes us to this jsFiddle example: https://jsfiddle.net/chrisvfritz/50wL7mdz/

The very first thing I did, I extended the template to be: {{message}} = {{extended}}. And the view came up empty. Why is it empty, if I’m just extending a template that has some properties already defined in it?

It was only after I added property extended into the model that I was able to see the proper view.

How come the entire model is ignored/skipped unless it is fully defined? This doesn’t make sense. Any complex view/template design starts by introducing elements one by one, many of which may be optional, and we cannot even see anything unless everythign has been defined.

This looks like the wrong approach.

Please don’t be too judgmental, I just wanted to share my impression after 5 minutes of playing with it, which I think still matters because this is how many newcomers are likely to percieve this framework.

[yyx990803]

Yes this is different from Angular, and it is intentional. It is required to explicitly declare all root-level reactive properties upfront. This has a few benefits:

1. Your data serves as the schema of your component state. When maintaining it later, by looking at your component definition you are able to instantly see what properties are available. If you simply dynamically add new properties at random places, it would be a maintenance nightmare, like maintaining a database without a schema.

2. This results in more predictable behavior, in particular when paired with type-checking systems.

3. It avoids excessive re-render that might be caused by adding root-level properties.

Finally, as a developer you should be able to choose what browser to develop in. If Chrome 44 is the only browser you can use at your job, that seems like a terrible decision on your companies part. Do all customers of your company use Chrome 44? Probably not.

[LinusBorg]

Well, the reasoning can be explained as follows:

• We cannot reproduce this behaviour with currently supported browsers in their latestest (auto-updated) versions.
• We have limited time and resources to reproduce problems on all possible system and browser compbiantions.
• Chrome Version 44, the version you seem to have this problem with (and maybe it’s a combination of v44 and some extension?), currently has a market share of 0.08%.
• The error you experience is not a bug from using Vue as intended, it only happens when you use Vue in a way you should explicitly not, and if your error does not appear, a dev warning would appear in its place. So there’s no danger of it making its way into production.

If we take all of this into account, it seems to me that it’s not worth our limited resources to try and hunt down a bug that is not reproducible for us, but may happen for 0.08% of users if someone pushed this wrong code to production.