I will disagree about ORM- there are already plenty of ORM and ORM-like frameworks out there for .NET, and I don't think the MVC team wanted to add another one.
Not sure about the routing being verbose. I'm (hopefully) close to finishing up a fairly complicated app with the framework, and routing hasn't been a problem for me.
I will definitely agree with point 12 though, but that's because the WebForms model causes brain damage if you use it for too long.
I will disagree about ORM- there are already plenty of ORM and ORM-like frameworks out there for .NET, and I don't think the MVC team wanted to add another one.
Not sure about the routing being verbose. I'm (hopefully) close to finishing up a fairly complicated app with the framework, and routing hasn't been a problem for me.
I will definitely agree with point 12 though, but that's because the WebForms model causes brain damage if you use it for too long.