Vue.js 2.1 Released • Hacker News Board

Re: Vue.js 2.1 Released

#101

Post by k__ » Wed, Nov 23, 2016, 9:05 PM UTC

kimshibal wrote: post #58

k__ wrote: post #12

Earlier quoted context omitted.

Hm, doesn't seem that much of a win for React users. The performance is compareable, but they went for templates instead of the "it's just JS"-philosophy of React. Reminds me of "the fear of turing complete templates"[0] Also, they mention their bindings are similar to MobX. I had the feeling MobX was a step back in the React eco-system, if I think about what Facebook wanted to achieve with Flux. But yes, overall it…

If you like JSX, please stick with React.

I think it's okay, makes finding markup in .js files much easier.

But I think I prefer t7, because it works 'native'

Re: Vue.js 2.1 Released

#102

Post by brlewis » Wed, Nov 23, 2016, 9:28 PM UTC

vbit wrote: post #82

I have some projects in Mithril - is it worth it port to Vue?

Speaking only for myself, I'm sticking with Mithril.

Re: Vue.js 2.1 Released

#103

Post by chinathrow » Wed, Nov 23, 2016, 9:33 PM UTC

Are there any migration guides from jQuery to Vue which are noteworthy?

Re: Vue.js 2.1 Released

#104

Post by [deleted] » Wed, Nov 23, 2016, 9:47 PM UTC

brlewis wrote: post #102

vbit wrote: post #82

I have some projects in Mithril - is it worth it port to Vue?

Speaking only for myself, I'm sticking with Mithril.

[deleted]

Re: Vue.js 2.1 Released

#105

Post by true_religion » Wed, Nov 23, 2016, 10:01 PM UTC

myf01d wrote: post #28

I am sorry if this sounds too ignorant, are frameworks like Vue.js (I actually read the guide and understood some wonderful things about its philosophy since I am actually developing backend mainly) or React, etc.. reasonable to use in websites in general (instead of jquery or taking some tasks from it) or they actually only reasonable for mobile web applications and SPAs? What about the SEO and search engine renderi…

Google will index sites that render their pages through Javascript. There are two caveats to be aware of:

1. It drops out if it takes more than 5 seconds to complete its operation and uses whatever is render then.

2. Indexing with HTML happens in near-realtime. Indexing with JS to HTML is delayed by about 1-5 days depending on the popularity of the site.

So if you're serious about it; you ought to heavily include metadata for Google to index during the first run through or place a bare bones HTML copy down.

Re: Vue.js 2.1 Released

#106

Post by buckbova » Wed, Nov 23, 2016, 10:15 PM UTC

> http://mithril.js.org/comparison.html

> Vue's implementation cleverly hijacks array methods, but it should be noted that Javascript Arrays cannot be truly subclassed and as such, Vue suffers from abstraction leaks.

Can anyone who knows how vue is implemented explain this statement?

Re: Vue.js 2.1 Released

#107

Post by bedros » Wed, Nov 23, 2016, 10:17 PM UTC

no1youknowz wrote: post #77

CharlesW wrote: post #62

For folks who haven't tried Vue yet, I just completed my first project with it and I'm really excited about using it more. Specifically, I used learning Vue as an opportunity to upgrade a simple jQuery-based SPA (with a PHP backend) to ES6, JS modules and Vue. It was a little hairy to bite off all of that stuff at once, but the Vue community was really helpful. In contrast to more monolithic frameworks I didn't have…

Thanks. With this coupon "CNETBF2016" it's now just $10 and I bought it at that price!

Thank you, I've been looking for vue.js courses

Re: Vue.js 2.1 Released

#108

Post by bedros » Wed, Nov 23, 2016, 10:17 PM UTC

CharlesW wrote: post #62

For folks who haven't tried Vue yet, I just completed my first project with it and I'm really excited about using it more. Specifically, I used learning Vue as an opportunity to upgrade a simple jQuery-based SPA (with a PHP backend) to ES6, JS modules and Vue. It was a little hairy to bite off all of that stuff at once, but the Vue community was really helpful. In contrast to more monolithic frameworks I didn't have…

Thank you, I've been looking for vue.js courses

Re: Vue.js 2.1 Released

#109

Post by spankalee » Wed, Nov 23, 2016, 10:28 PM UTC

untog wrote: post #68

myf01d wrote: post #28

I am sorry if this sounds too ignorant, are frameworks like Vue.js (I actually read the guide and understood some wonderful things about its philosophy since I am actually developing backend mainly) or React, etc.. reasonable to use in websites in general (instead of jquery or taking some tasks from it) or they actually only reasonable for mobile web applications and SPAs? What about the SEO and search engine renderi…

I can't speak to Vue, but React is overkill for many sites. The virtual DOM etc is incredibly useful for sites that update the page very frequently, but if the only thing you're making is a static site and a contact form, you don't need React. That said, I do like the React model of creating components (and suspect this is why so many people use it when it's unnecessary). I'm looking forward to browsers implementing…

Chrome, Safari, and Opera (because of Blink) have implemented Custom Elements and Shadow DOM. Firefox appears to be working on it, and for Edge it's high priority, so things are coming along nicely :)

edit: The polyfills are also very viable. I know sometimes people knock polyfills, but they're really just libraries that implement the component model and encapsulation that frameworks generally have to, but they go away over time.

Re: Vue.js 2.1 Released

#110

Post by dalailambda » Wed, Nov 23, 2016, 10:30 PM UTC

untog wrote: post #68

myf01d wrote: post #28

I am sorry if this sounds too ignorant, are frameworks like Vue.js (I actually read the guide and understood some wonderful things about its philosophy since I am actually developing backend mainly) or React, etc.. reasonable to use in websites in general (instead of jquery or taking some tasks from it) or they actually only reasonable for mobile web applications and SPAs? What about the SEO and search engine renderi…

I can't speak to Vue, but React is overkill for many sites. The virtual DOM etc is incredibly useful for sites that update the page very frequently, but if the only thing you're making is a static site and a contact form, you don't need React. That said, I do like the React model of creating components (and suspect this is why so many people use it when it's unnecessary). I'm looking forward to browsers implementing…

While the virtual DOM is a component in React's popularity, the main thing that I believe people use it for is the functional, one way data flow it allows you to use combined with the component model.