I decided to give up on Angular, a bloated over-engineered and complex to learn mess! I cut my teeth with Angular and made a lot of money consulting as a Angular dev. I drank the kool-aid and use to champion it. Now I know better, I would never recommend using Angular for enterprise dev, too much time wasted fixing breaking changes. The larger the project the more painful and wasteful these upgrade cycles are, there is angular, rxjs, ngrx and yes crappy angular material with its own set of bugs that never get fixed or accessibility issues that have gone unfixed.
With Angular the developer is forced to (keep) re-learning the eco-system over and over as none of this over-engineer complexity was designed with the developer in mind.
I switched over to Vue.js, it is smaller, a lot faster with rendering, forget the Ivy hype! Plus Vue.js is really well designed and doesn't get in the way like angular does. Easy to learn and to remember skills learned, the routing and global store (vuex) is a joy to use! Gone are the boilerplate coding in Angular + batteries! With Vue.js 3.0 out, switching away from Angular has never been a saner choice!
Between AngularJS, Vue and React, my best experience was with VueJS.
I never moved to Angular it was too much of a shock for me, what if I had many large scale projects already on AngularJS... it would be painful.
And the whole concept of Angular feels like a monolith, like Dojo toolkit and Sencha ExtJS, hard to turn around when things change (e.g. mobile screen size introduced).
Vue 3 with Vite3/Snowpack, ES Modules etc. is a game changer. I mix it with HTML Custom Elements, and use Javascript native APIs to reduce exposure to technical debt and breaking changes in dependencies.
Even VueJS ecosystem is not immune to changes... the Vee-validate is one such example, major version change requires rewrite of the validation code... imagine if just one application has 20 forms and each form has 20 fields... One would be better off working with native HTML5 Validation.
All those supporting UI frameworks like Bootstrap, Ant Design, Material UI, etc... for vue/react/angular/etc were designed as monoliths...
Moving to HTML Custom Elements (aka Web Components) should help make your UI less susceptible to underlying vue/react/angular/etc framework changes...
At the end of the day I do not want to revisit and rewrite what I have written.
The only big advantage I know of having to keep rewriting and updating is that this will help keep one employed perpetually...
👨🏫 Co-Founder of This is Learning, Organizer of AarhusJS
✍️ Writer, Speaker, FOSS Maintainer 📗 Author
🏆 Microsoft MVP 🌟 GitHub Star
🌊 Nx Champion 🦸 Angular Hero of Education
I decided to give up on Angular, a bloated over-engineered and complex to learn mess! I cut my teeth with Angular and made a lot of money consulting as a Angular dev. I drank the kool-aid and use to champion it. Now I know better, I would never recommend using Angular for enterprise dev, too much time wasted fixing breaking changes. The larger the project the more painful and wasteful these upgrade cycles are, there is angular, rxjs, ngrx and yes crappy angular material with its own set of bugs that never get fixed or accessibility issues that have gone unfixed.
With Angular the developer is forced to (keep) re-learning the eco-system over and over as none of this over-engineer complexity was designed with the developer in mind.
I switched over to Vue.js, it is smaller, a lot faster with rendering, forget the Ivy hype! Plus Vue.js is really well designed and doesn't get in the way like angular does. Easy to learn and to remember skills learned, the routing and global store (vuex) is a joy to use! Gone are the boilerplate coding in Angular + batteries! With Vue.js 3.0 out, switching away from Angular has never been a saner choice!
Between AngularJS, Vue and React, my best experience was with VueJS.
I never moved to Angular it was too much of a shock for me, what if I had many large scale projects already on AngularJS... it would be painful.
And the whole concept of Angular feels like a monolith, like Dojo toolkit and Sencha ExtJS, hard to turn around when things change (e.g. mobile screen size introduced).
Vue 3 with Vite3/Snowpack, ES Modules etc. is a game changer. I mix it with HTML Custom Elements, and use Javascript native APIs to reduce exposure to technical debt and breaking changes in dependencies.
Even VueJS ecosystem is not immune to changes... the Vee-validate is one such example, major version change requires rewrite of the validation code... imagine if just one application has 20 forms and each form has 20 fields... One would be better off working with native HTML5 Validation.
All those supporting UI frameworks like Bootstrap, Ant Design, Material UI, etc... for vue/react/angular/etc were designed as monoliths...
Moving to HTML Custom Elements (aka Web Components) should help make your UI less susceptible to underlying vue/react/angular/etc framework changes...
At the end of the day I do not want to revisit and rewrite what I have written.
The only big advantage I know of having to keep rewriting and updating is that this will help keep one employed perpetually...
Yes but compare the job postings and vue comes in last.
This certainly depends on the region of the world you're looking for jobs in.
I ditched Angular since 2015, right when they throws version 2+ at alpha.
I'm moving to Svelte