No one said anything about moving away from server side templates. I don't know why .NET developers get so confused over this subject. By modern I mean using a

No one said anything about moving away from server side templates. I don't know why .NET developers get so confused over this subject. By modern I mean using a very popular language in a domain that specifically has that language as its primary and first most choice in that domain for every single aspect of that domain's development. From the pool of developers you can choose from, to where those tools and applications can be run, to how you construct your web applications. On a new project that doesn't have historical roots in using the Razor view engine, again, what is Razorscript bringing to the table that other server side templating languages/frameworks are not? Why would you willingly choose to use a view engine and templating language that costs you in functionality, reduces the flexibility of your views, reduces the amount of programmers that can work with it, and causes really really bad start up times/cache miss hits (lol @ precompiling your views, so you can restart your app pool for tiny little changes)? You don't need an SPA to move away from Razor. It's quite the opposite: you better have a damn good reason to continue to use the Razor view engine.