I feel like the design is heavily influenced by Angular (which is good, since Angular makes many good decisions). Is the intention of Vue to be a lighter-weight alternative? Are there features and design decisions that Vue makes differently? (E.g. the model concept seems simpler in Vue)
Since first toying with Ember early on, I've decided that a good test of many of these MVVM libraries is to see how we can easily share data across multiple views.<p>I'm not entirely sure how that would work Vue.js. I suppose at some point you could have<p>var parent = new Vue(options);
parent.$data = [object,object,object];<p>var child = new Vue(options);
child.$data = parent.$data[i];<p>seems simple enough, what's your scratch test before trying a new library?
Is the use of of custom attributes a good practice? (example: <div v-text="message"></div>)?<p>I thought the data-* attributes were the recommended way (<a href="https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_data_attributes" rel="nofollow">https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Usin...</a>).
Great performance. Would sacrifice some code clarity and readability to get theses numbers (<a href="http://vuejs.org/perf/" rel="nofollow">http://vuejs.org/perf/</a>).<p>My only concern with all these new libraries is how long they will be around.
After reading the documentation, I have to say this seems to be a nice medium b/w angular and knockout. I love how the api is really small and you just use plain js objects just like in knockout.js.