Scott Gu's blog has a much more comprehensive look at this engine:<p><a href="http://weblogs.asp.net/scottgu/archive/2010/07/02/introducing-razor.aspx" rel="nofollow">http://weblogs.asp.net/scottgu/archive/2010/07/02/introducin...</a>
They really needed to do this. The ASPX view engine just felt like they took existing code and shoved it in to the MVC framework.<p>A fresh start was needed, and it looks great.<p>It'll be interesting to see how they incorporate unit testing.
Razor is a major step in the right direction. Spark view engine still offers enough punch for me not to switch to Razor just yet. The stuff that you can do with bindings and the convention over configuration stuff are still killer features for Spark.
Am I the only person who sees this and says, “Congratulations guys, nice work! Now if only you had done this in 2006, you might be on the cutting edge.” I don't mean to disparage their work, I am sure that is is technically sound and well-considered.<p>It seems like, among the leading-edge developers, this kind of tempting is rapidly being eschewed by newer techniques.