Not for existing projects - I see no reason to move an existing project to a new framework until the current framework can't do something that needs to get done.

That said, I have strong feelings about AJS 2 being almost a completely different framework and if / when I need to move my existing AJS 1 websites to a new framework, or starting a new project, I'll be choosing something other then AJS 2.

Yes, I am in for ditching Angular for React. I am not comfortable with Angular 2.0. React does the componentization more elegantly.

The answer (as usual) is "it depends".

• do you/does your team like Angular 2?
• are you/is your team proficient in an alternative or keen to learn?
• are you maintaining existing apps or building new projects... the point being what's your maintenance situation? If you are maintaining a product, how much will it cost to convert what you have into the alternative? OR, how much will it hurt to maintain two somewhat-different code bases?

We've just ditched Angular for React, for whatever it's worth. It works better for our team and we don't have enough Angular in production for the legacy conversion to be a problem.

React and Vue are more awesome

We move to Aurelia