The short answer is that, in some sense, yes, AngularJS is killing ASP.NET MVC. But that doesn’t mean you should jump in the AngularJS boat for your next project, which is hard for me to say since I consider myself an AngularJS advocate.
An interesting theme to discuss
First, not every website has to be a SPA, and therefore, doesn’t need to be built with AngularJS. Yes, I’ll agree there’s a tendency towards building websites as SPAs. However, think about administrative websites which are not very interactive, like an ERP. In my previous project I worked with a medical laboratory administrative website, which was not using AngularJS and it worked fine. It fulfilled the requirements and companies bought the product.
There was no need for AngularJS. Now consider the opposite case, which could be your typical pizza ordering website, where you build your own pizza and pick the toppings. This type of website fits the SPA architecture, and AngularJS is a good fit.
Moreover, consider that AngularJS has a learning curve, and I’ve seen some .NET developers struggle with AngularJS. This is something to think about if you are planning to implement AngularJS in your next project. More specifically, make sure the team is trained correctly if you’re going to use this technology.
AngularJS gives you tools to use in the form of controllers, modules, directives, templates, services and so on; but they can be misused and your code can potentially become a big ball of mud.