Great article!
Vadim Zelenin
11

If by AngularJS you mean Angular 1, then I do think it does not fit into ≥ES6, [mainly, but not only] due to now we having classes and modularization. Services, factories, providers, they all stopped making much sense. Controllers were fine, but we never really had much separation between view and controller, so they ended up being part of the same thing (with the template/view handling how the state is rendered, and the controller handling how the state changes). Directives, which were barely used, could have replaced controllers for almost anything UI/UX related (making the controllers “slimmer”), but never did, everybody just used controllers for everything.

And all of that can be easily replaced with ≥ES6 and libraries like React.

You might say AngularJS was much more than just that. That’s true. But ES6 gave us fetch (which replaces $http) and Promise (which replaces $q and promise apis) — we even have Bluebird, if you feel the need for better promises; we have underscore, lodash, lazy.js, ramda, and many other utility libraries to replace most (all?) of the utility functions present in AngularJS. Well, everything in AngularJS can be replaced with better stuff.

What was wrong in AngularJS’s concept? Trying to be everything at once. One thing gets deprecated, the whole framework has the risk of getting deprecated. And I see Angular 2 going down the same path. AngularJS was awesome! Now we have better options, so I don’t see Angular living much longer.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.