Forum Overview :: BIT.TRIP RUNNER :: It is being used for traditional sites.

[quote name="Fullofkittens"]At my office we wrote an enterprise video portal using Angular for frontend stuff. Our latest web thing came out this week and is in React. (All with Azure backend, we're an MS shop at heart.) The pitch for Angular is that it's client-side, it's easy to write tests for, and front end people find it easier to style. As far as "why not ASP.NET MVC," not being married to the MS stack is inherently valuable to some people, too. If you're using Angular for frontend you might be part of the Node/NPM ecosystem* which is a bit more magical and fun and less work than the .Net/Nuget ecosystem. Writing web apps in the MS stack feels like driving a tank compared to JavaScript's rocket cars. All the web devs I know fall into two camps: people who prefer React and people who think they would probably prefer React if they took the time to learn it but are still using Angular. I do not know anyone that looked into either of those and decided that ASP.NET MVC was preferable. (*There's also the possibility of porting JS applications to the desktop - cross-platform! - using Electron; that's not a thing with ASP.NET MVC apps. That's how both the Slack client and VS Code work.) [/quote]