I'm as guilty as anyone else on the team for pushing forward to Avalon/WPF. The truth is that much of the team was just exhausted an wanted to do something else

I'm as guilty as anyone else on the team for pushing forward to Avalon/WPF. The truth is that much of the team was just exhausted an wanted to do something else. It was people higher in the chain that dropped the ball on IE completely. The funny thing is that HTML5 does much of the stuff we originally wanted to do with Avalon. We just didn't have the structure, people or support to do it within the standards process. Also the W3C was a different force then and I suspect fast innovation driven by Microsoft wouldn't have been accepted. (Karma's a bitch.) Anyway when much of this became clear I moved on to google. :) (hi Fil! When can we get you on board?)