Yes Tim, the downfall of AngularJS was the over zealous Dependency Injection system which disallowed new features popping up in JavaScript. The concept that we could not have a library of JavaScript class models and use the new keyword, was a gross over-site on the design. If I recall it didn't yet support the new JavaScript module system either. In essence, AngularJS hijacked JavaScript to implement it's own opinion of how things were to be done. It used JavaScript to create it's own DSL.
I was so soured on AngularJS that I didn't want to learn Angular. Instead I reached out to React at the time. But my next job was all Angular, and I was relieved to find the new design as good as it was. Had it continued to be like the old AngularJS I would have had to find another job. I simply won't work in AngularJS unless a company is migrating to the new...
Thanks for this excellent article.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes Tim, the downfall of AngularJS was the over zealous Dependency Injection system which disallowed new features popping up in JavaScript. The concept that we could not have a library of JavaScript class models and use the new keyword, was a gross over-site on the design. If I recall it didn't yet support the new JavaScript module system either. In essence, AngularJS hijacked JavaScript to implement it's own opinion of how things were to be done. It used JavaScript to create it's own DSL.
I was so soured on AngularJS that I didn't want to learn Angular. Instead I reached out to React at the time. But my next job was all Angular, and I was relieved to find the new design as good as it was. Had it continued to be like the old AngularJS I would have had to find another job. I simply won't work in AngularJS unless a company is migrating to the new...
Thanks for this excellent article.