> Despite being a full rewrite, the API is largely compatible with 1.0 with the exception of some intentional deprecation. This guy gets it.
[deleted]
Announcing Vue.js 2.0
21–30 of 59 posts
Re: Announcing Vue.js 2.0
#22Congratulations on your launch, but I couldn't tell what Vue was from this announcement post. I wish articles like this could include even just one sentence at the beginning that looks like this: Vue.js is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. (pulled from their GitHub README, which I was only able to find because of the comment here on…
The main vue.js web site is here: http://vuejs.org/
That's still one click too far. It wouldn't cost anything to add a single line of text on top, while arguably persuading more newcomers to try and learn Vue.
Which is great, BTW, I used it in a couple of projects with LiveScript and it was a pleasure. It doesn't assume much about your code and you can fit it in any kind of architecture you happen to have. Good to see a progress here!
EDIT: wait, it's already there (the mention what Vue.js is) in the article:
> In case you’ve never heard of Vue.js before: Vue.js is a front-end framework that consists of a core view layer and accompanying tools & supporting libraries. You can read a high-level introduction to what makes it different here.
Re: Announcing Vue.js 2.0
#23Vue.js is amazing. I've been using it on one of my side projects and I've been so productive with it that I can't see myself ever using anything else. It's like a mix of React, Angular and Knockout all in one package.
Anything in particular you like about it? I'm trying to find a reason to learn Vue, but I like React so damn much!
I love it since it somehow feels like a lighter and less opinionated version of Angular. I could basically guess myself to how to use it, and there's pretty few pitfalls/gotchas.
Also there's a Chrome Devtool for it and the debug mode is helpful.
Re: Announcing Vue.js 2.0
#24Earlier quoted context omitted.
The main vue.js web site is here: http://vuejs.org/
That's still one click too far. It wouldn't cost anything to add a single line of text on top, while arguably persuading more newcomers to try and learn Vue. Which is great, BTW, I used it in a couple of projects with LiveScript and it was a pleasure. It doesn't assume much about your code and you can fit it in any kind of architecture you happen to have. Good to see a progress here! EDIT: wait, it's already there (t…
[deleted]
Re: Announcing Vue.js 2.0
#25I'm not an expert on either, but my understanding was that Vue's advantage over React was that since it had no virtual DOM you were free to manipulate the DOM more freely without running into trouble. Now that Vue has its own virtual DOM it is harder for me to see the difference from React. Many of the positives listed both here and on the Vue site could also be said about Knockout, which I still am currently using at the moment (though I'm likely moving to React soon).
Re: Announcing Vue.js 2.0
#26I'm not an expert on either, but my understanding was that Vue's advantage over React was that since it had no virtual DOM you were free to manipulate the DOM more freely without running into trouble. Now that Vue has its own virtual DOM it is harder for me to see the difference from React. Many of the positives listed both here and on the Vue site could also be said about Knockout, which I still am currently using a…
Oh, it has proper Virtual DOM now? I'll have to check it out. We've been using React for a Web app that needs to render and completely re-render (new columns etc.) lots of data - no hot updates - Vue was frustratingly slow (5-10 seconds), to the point where we initially had to use an isolated vdom solution (Snabbdom) that became messy fast. React is amazing, so not sure if we'll end up going back to Vue for anything data-driven (tabular).
Re: Announcing Vue.js 2.0
#27I'm not an expert on either, but my understanding was that Vue's advantage over React was that since it had no virtual DOM you were free to manipulate the DOM more freely without running into trouble. Now that Vue has its own virtual DOM it is harder for me to see the difference from React. Many of the positives listed both here and on the Vue site could also be said about Knockout, which I still am currently using a…
Knockout's perf on large re-renders is below average: http://mathieuancelin.github.io/js-repaint-perfs/knockout/ It also doesn't allow you to use programmatic render functions, nor does it have server-side rendering.
Vue 2.0's vdom implementation is mutation resistant - as long as you don't replace the element directly controlled by Vue (same as 1.0), the rendering will not run into problems. If you are really concerned you can always create a custom component that returns an empty element so that you can do arbitrary manipulations inside.
Re: Announcing Vue.js 2.0
#28I'm not an expert on either, but my understanding was that Vue's advantage over React was that since it had no virtual DOM you were free to manipulate the DOM more freely without running into trouble. Now that Vue has its own virtual DOM it is harder for me to see the difference from React. Many of the positives listed both here and on the Vue site could also be said about Knockout, which I still am currently using a…
Oh, it has proper Virtual DOM now? I'll have to check it out. We've been using React for a Web app that needs to render and completely re-render (new columns etc.) lots of data - no hot updates - Vue was frustratingly slow (5-10 seconds), to the point where we initially had to use an isolated vdom solution (Snabbdom) that became messy fast. React is amazing, so not sure if we'll end up going back to Vue for anything…
Vue 2.0's vdom is actually forked from snabbdom ;)
In particular if you don't need hot updates, adding Object.freeze() to your data will make the rendering 2x faster than React.
Re: Announcing Vue.js 2.0
#29Great job!
Re: Announcing Vue.js 2.0
#30Riot is a very similar library, worth a look.