[kabes]

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".

[seanwilson]

> 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?

[kabes]

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