I'm using IE, and Start the tour doesn't work at all.
What a nice guy! I hope the Visual Studio team sees this, and starts thinking harder about accessibility. Blind programmers can be as productive as sighted ones, since most programming and debugging is text based. Only the tools are lacking.
I would like to hear Christopher expand on this transactional programming idea for application programming (not stored procedures) for simplifying hard exception handling, such as OOM. What sort of concepts would the developer be dealing with? How would the application be structured for "rip-down" componetization?
How would the conflict between declarative and imperative developement styles be resolved.
This sounds great, but what exactly is this non-traditional execution Christopher is speaking of? AOP or a derivitive?
I see there is a great deal of power at that level, but I am not sure what might be done there.
One thing I would like to see is method tracing. Selectively turn on a trace-log using regular expressions matching member names, and type/namespace filtering, with indenting according to call depth, and possibly logging argument values as well. I am used to using this type of tracing in older object oriented environments.