Regarding you first point, it was the community's perception after last year's ngEurope, but not so much after this year's ngConf. With the current focus on co

Regarding you first point, it was the community's perception after last year's ngEurope, but not so much after this year's ngConf. With the current focus on component-based design in Angular 1.x, the meat of your app would be fairly easy to move to angular 2. Much of the job involves removing code and I believe it can, and will be automated in due time (with some shortcomings, to be sure). Moreover, the core team has put a focus on making 1.x modules compatible with 2.0 and 2.0 modules compatible with 1.x so that you can migrate progressively. Unlike with React, you don't start off with a clean slate and that's a major shortcoming, but I think right now Angular is still a solid choice of client-side framework, mainly because of its enormous community and iteration speed. The main trouble is, you need to be following the latest developments and best practices, otherwise you'll probably end up Doing It Wrong™.