[barefoot]

“James [the client CTO] mentioned multiple times that he wants a future-proof technology, and he is not in favor of Angular because it has a bad reputation after AngularJS got deprecated.”

Few things in our industry are future-proof (or even future-resistant) and the stated indictment against Angular over the v1 to v2 changes is unreasonable even at the time.

These decisions are important but it looks like the author lost (or maybe never had) significant influence over them. The ability to influence key stakeholders over critical design decisions using rational (and evidence based) arguments is an important precursor to a successful project. It’s still possible to ship large projects without it, but it makes for a very challenging environment.

Optimized headline aside, I appreciate this summary because it highlights some of the nontechnical challenges in building larger applications.

[alunchbox]

Strange that this is the only point about Angular that gets brought up majority of the time. Angular team could have saved themselves a ton of trouble by just renaming Angular 2+ to a different name and it would have solved this public perception.

All of these front-end frameworks are open-source so they're all future proof, fork and continue fixing and implementing your own stuff into it...