nice
Announcing Vue.js 2.0
51–59 of 59 posts
Re: Announcing Vue.js 2.0
#52nice
Re: Announcing Vue.js 2.0
#53Vue.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.
Agree, it's absolutely my go-to whenever building anything one-page-ish that doesn't need a full framework.
Re: Announcing Vue.js 2.0
#54Thanks for all of your work Evan :)
Re: Announcing Vue.js 2.0
#55Wonderful! Vue is my favorite
Re: Announcing Vue.js 2.0
#56does anyone write single-file Vue components in Emacs? If you do - how do you configure it to have language-dependent things like flycheck and syntax highlighting working correctly in different blocks of the component file?
Re: Announcing Vue.js 2.0
#57> Despite being a full rewrite, the API is largely compatible with 1.0 with the exception of some intentional deprecation. This guy gets it.
Yes, backward-compatibility is the key to keep a framework long-living.
I was trying to adopt Angular 1.x, but wait, the code I'm going to write will be deprecated soon?
Re: Announcing Vue.js 2.0
#58Re: Announcing Vue.js 2.0
#59I'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 concer…
That's exactly why I am switching away from Knockout. I loved every minute of it, but there are features I simply can't deliver on because the perf is too low. There are all sorts of hacks I could do to get around it but that is really going to slow me down.
TBH It's not really the rendering that is slow in my experience. It's the fact that every binding attaches an event handler to the DOM. This can take up to 10s for a reasonably sized grid in IE.