ViewData vs. ViewModel... that's sort of unnecessary complexity to MVC. My vote is for ViewDataDictionary to inherit from IDynamicMetaObjectProvider so that we can have the best of both worlds with 1 concept. But that's just me....
Abstracting your favorite IoC container is a really terrible idea. Why would you use Unity over StructureMap over NInject, etc if you're just going to abstract away the power? Doesn't make a lot of sense from an architectural perspective. Why take on an
additional dependency that is just an abstraction on IoC and dependency containers, wire-ups, etc?
And another thing... infered actions. Why would you use MVC if you're just returning a view? Smells exactly like webforms at that point.
No, Laura this does not prove global warming. It has yet to be proven that our emmissions
cause global warming. CORRELATION DOES NOT PROVE CAUSATION! THIS IS THE
FUNDAMENTAL PRINCIPLE OF SCIENCE! THIS IS AN ISSUE OF SCIENCE, NOT POLITICS!
Here's the problem. C9 pays a LOT of money in bandwidth to be sent over to countries nowhere near the United States where their servers probably are. With Azure, C9 would have the ability to serve many more users and allow for better scaling on the data