@chriskacerguis: What I am trying to say for 2 years now is “The OPS UI IS past the point of no return” with the Angular rewrite.
The OPS UI is big and a rewrite takes long. Important part of the rewrite is decoupling things so that future rewrites are less painful. But the rewrite has to be finished.
At the same time the things around envolve and we have to react to that. The idea is to support Angular 1.x, Angular 2/4 and React in the OPS UI.
Angualar 1.x is a must because we ARE PAST THE POINT OF NO RETURN.
Angular 2 is what we see as a future with an existing, proven and tested transition path. Angular 1 and 2/4 can coexist, people and companies use those together.
React is the cool kid on the block. It is being used by other projects in the company, there will be a lot of code that we could benefit from written in React. There’s a way to host React component in Angular apps and we can do that in OPS UI too. We can enable other teams to do their stuff in React inside OPS UI.
Angular 1.x, Angular 2 and even React are going to receive more or less support from Patternfly.
Now tell me, why would someone want to add VueJS in the mix? Unless you really care only about SUI or don’t understand the situation you cannot be serious!
I suggest that your team spend a sprint or two on OPS UI to get a realistic picture and we get to the same page. I can understand that you might not believe that I have a realistic picture about SUI but I believe noone doubts that @himdel has it.
Guys, if the 3 of you in SUI decided that you don’t want to do Angular, try pushing React. I would not agree, but would not see it as such a huge nonsense as using VueJS. And I believe you will find more people that will share this view.