AFAIK you do not gain/lose anything picking one or the other.
Something I can think of though is that components have the advantage of being reusable if you specify the template in the component "template" property. Then you can use the same component in multiple places via it's named <tag> in your html, whereas with a new Vue() you are limited to the element that you bind it to.
I would still say 1 Vue VM per website, not per page
@emilmoe Well it really depends. If you're not doing a single page app, then you can't avoid having multiple instances around your website. Especially if you are just dropping Vue in for a bunch of single components in different pages.
@Neugierdsnase_ I'm not sure what you mean by "one Vue per page". If you were meaning have 1 Vue instance bound to the whole page and do all of your logic in one component, that can get messy very fast. It all depends on what you're trying to achieve, but things like vuex can help keep your state in order while using multiple components.
Ozzie Neher
Full Stack Dev
AFAIK you do not gain/lose anything picking one or the other.
Something I can think of though is that components have the advantage of being reusable if you specify the template in the component "template" property. Then you can use the same component in multiple places via it's named
<tag>in your html, whereas with anew Vue()you are limited to the element that you bind it to.