Live data from Hacker News

Vue.js 2.1 Released

github.com

71–80 of 126 posts

Re: Vue.js 2.1 Released

#71
post #65

I'm looking to move a few projects from Angular 1. What do developers think of migrating to Angular 2 vs Vue for this? I've played with Angular 2 but can't shake the feeling that it's overly complex.

Well, it might help if you said why you're looking to move from Angular 1. What problems do you have with it? How many developers are working on the project? Do you use libraries like angular-material? ... There are a thousand factors why you'd chose one above the other. I would just be very wary of comments like: "Definitely framework X".

> Well, it might help if you said why you're looking to move from Angular 1. What problems do you have with it? How many developers are working on the project? Do you use libraries like angular-material? ...

Just that as time goes on Angular 1 is going to fall out of support in general and for popular libraries so it might be best to switch sooner rather than later before we get more entrenched in Angular 1. Switching to another framework wouldn't be a massive undertaking right now but probably would be later. Typescript is a great feature too but you can use this in Angular 1 somewhat as well. Any thoughts?

Re: Vue.js 2.1 Released

#72

I'm looking to move a few projects from Angular 1. What do developers think of migrating to Angular 2 vs Vue for this? I've played with Angular 2 but can't shake the feeling that it's overly complex.

Angular 2, not worth it. We made our decision to migrate an old Angular 1 app to Vue.js. Best decision ever.

> Angular 2, not worth it. We made our decision to migrate an old Angular 1 app to Vue.js. Best decision ever.

Can you elaborate? I've used Angular 1 a lot, Angular 2 a little and Vue not at all. What makes Vue better?

Re: Vue.js 2.1 Released

#73
I still wonder why they moved the events from the constructor to the instance...

Before 2.0:

new Vue({ el: "#el", data: someData, events: { myevent: function(){} } });

after 2.0 :

vm.$on('myevent', function () {})

Re: Vue.js 2.1 Released

#74
post #42
post #35

Earlier quoted context omitted.

From personal experience for general web-sites like blogs, etc. it's better to do them old way, you don't need to worry much about seo, caching, precompilation, etc. But business apps huge community-like ones, and big shops benefit a lot from frameworks like that. But you should always base your decision on cost of implementation, support, etc.

Thanks, I am more interested in developing social websites with modern look and more performance, I mean like the design of medium.com or hashnode.com, I think they do render the first page fully canonical HTML, and then every subsequent request is rendered using the js framework GETing some JSON which gives more space to the server to do other work. I am really interested in this approach but I fear about the SEO an…

Take a look at russian vk.ru

It's lighting fast compared FB and does all the same things. Really neet. FB makes my laptop literally over heat.

Re: Vue.js 2.1 Released

#75

I'm looking to move a few projects from Angular 1. What do developers think of migrating to Angular 2 vs Vue for this? I've played with Angular 2 but can't shake the feeling that it's overly complex.

You may want to check out Aurelia too. One of Angulars main devs left the Angular Team because of its direction and build Aurelia the way Angular should have been. I played with it a bit and what's awesome about it that you just write plain JS most of the time. No weird stuff like JSX and whatever. Docs arn't that great tho

It's worth noting that the developer who split from the Angular team to create Aurelia was also the developer of Durandal, which is quite a nice (and underrated) framework.

Aurelia is a sort of the spiritual successor to Durandal.

Re: Vue.js 2.1 Released

#76
post #41

Earlier quoted context omitted.

We're using Vue and its router in production since 1.x, so I'm not sure where you got that impression...

I would like to know more about your use of Vue and the router in production. Tips/best case guidelines?

If you have a relatively large app and having URLs makes sense, the router is a no brainer.

No real tips; the vue-router documentation is excellent.

If you're coming from Vue 1, the only thing that did confuse me is that the router hooks have changed. The router now listens on `beforeRouteEnter` and `beforeRouteLeave` and these hooks only get triggered once per route change. Therefore, to listen to query changes on a route you need to watch the `$route` object.

Re: Vue.js 2.1 Released

#77

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!

Re: Vue.js 2.1 Released

#78

Earlier quoted context omitted.

here's an link[0] to a comparison with react, angular 1 and others. [0] - https://vuejs.org/v2/guide/comparison.html

I loved how they did that! They actually invited the other experts to review and feedback on their declarations to ensure their work was honest and had integrity. Never seen that before. Have you? Also I wished it was clear if this doc was updated with Vjs2 or if it's 1.x or what. That's not clear anymore and they need to sort that out or the integrity is lost.. by accident, but still lost.

my respect for the project grew immensely (because it showed me that they really cared and it was not another "me too because I can and I have my own way of doing things" project).

Re: Vue.js 2.1 Released

#79

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!

Re: Vue.js 2.1 Released

#80
post #65

Earlier quoted context omitted.

Well, it might help if you said why you're looking to move from Angular 1. What problems do you have with it? How many developers are working on the project? Do you use libraries like angular-material? ... There are a thousand factors why you'd chose one above the other. I would just be very wary of comments like: "Definitely framework X".

> Well, it might help if you said why you're looking to move from Angular 1. What problems do you have with it? How many developers are working on the project? Do you use libraries like angular-material? ... Just that as time goes on Angular 1 is going to fall out of support in general and for popular libraries so it might be best to switch sooner rather than later before we get more entrenched in Angular 1. Switchin…

Well, they're not that far apart (vue 2 and angular 2). They're both component based frameworks with a very comparable templating system. So you'll be able to create the same things in more or less the same manner with both frameworks.

The main difference is that angular 2 is a bit more enterprisey. It's a bit more bloated (but also more complete) and if you're a small team with a not too large app, you may find it introduces too much overhead. If you're a larger team with a larger app you'll really benefit from angular 2.

One thing that speaks for angular 2 has is their ngUpgrade module, which allows you to gradually upgrade your angular 1 app, which you may find useful.

There's a (somewhat biased IMO) comparison by vue itself here: https://vuejs.org/v2/guide/comparison.html#Angular-2

Post reply on HN