The behavior you guys were talking about where redundant requests to fill or refill a cache entry can cause severe performance degradation is called "dogpiling." Glad to hear that anti-dogpiling is in effect on 9!
Good to see ASP.NET MVC talk on 9. Time to go check out Preview 4.
I thought ASP.NET MVC supported multiple view engines, not just ASP.NET, e.g., NHaml, NVelocity, XSLT, your own if you felt like building one. Check out
MVC-Contrib @ CodePlex for some community-driven, ASP.NET MVC-related projects.
With regards to the dynamic typing-static typing dichotomy, it is not either-or. It is not only-but also. We want not only the affordances of dynamic typing but also the assurances of static typing. Type inference sorta fakes us out into believing that it
provides this, but it's still static typing, and there are limitations to that approach that cannot be worked around until changes to the type system are made.
Java and C# have been around for a while, long enough to where people will grumble if you make too many changes to the language. If it is impossible to make changes to the language without incurring "-1000" penalties, then maybe it's time for a new language
(or perhaps an old one whose time hadn't quite yet come...) to step up and pave the way for programming language innovation. Better ways of getting the job done is the goal.
Another easy way to get black-on-white: the COLOR command. COLOR F0 will get you black on white. COLOR /? for more details.
Coincidentally, this video had an excellent demonstration of how IntelliSense can screw you up when you try to enter lambda expressions in C#. When Alex tried to enter c => c.City == "London", IntelliSense "helpfully" suggested case even though it makes no
sense to enter the case keyword at that point (he wasn't even in a switch statement). I'm learning to hit Esc to cancel the IntelliSense, but I would prefer not having to do so. Please fix this.
standard but enjoyable nonetheless!