Golly, I love this job.
Okay, before you read any further, go read the tagline of this blog. In case you’re reading it through RSS, I’ll paste it here: “This is the personal blog of Chris Wilson, Platform Architect of the Internet Explorer Platform team at Microsoft (and ex-Group Program Manager).” Underscore that “personal” bit.
Okay, now go read the last line of the first paragraph of my last post. Again, for your convenience: “Consider the rest of this post to be only my opinion, because I haven’t even run it by the other people on the team.” Consider that to be true of this post as well. (This post, too, has not been run past anyone here.)
Now we’ve established that this blog, and the last post as well as this one, are just me talking, and not the “Voice of Microsoft” (said in your best James Earl Jones voice).
Brendan, my post was my opinion, and (I thought) clearly labelled as such. Sorry you take it personally, and you should feel free to disagree with my opinion. Please don’t call me a liar, though – or at least, credit me with enough intelligence to make my own lies up, and not simply parrot those of others. In my opinion, the current ECMAScript 4 proposal would be disruptive to the web ecosystem, and I don’t think the priorities driving its evolution have been placed where I would place them. (E.g., as I said before, I’d like to see domain security addressed in the core language.) That said, it’s my opinion.
When I made a reference to “shouting down dissent,” I thought again that I was being clear that I was referring more to the string of blog comments made by you and others immediately to any blog post that seemed to question the righteousness of the current ES4 proposal, than to functioning of the TG-1. The response to this post, and others in the last day or so, doesn’t make me want to retract that. I was not referring to actual shouting in TG-1 meetings – I’d have to agree with your characterization of “vigorous debate” – though I think you seem a mite personally hostile to Microsoft. That’s a personal-interaction observation, though, and not reflected in minutes, and therefore not worth much.
No, I never tried to “prove” that ES4 requires a new VM. I said 1) ScreamingMonkey pushes a new VM into IE, and will cause ES4 scripts to not be run in the same VM as ES3, within IE. (True, yes? Please tell me if I’m wrong here, as I’m (obviously) not as intimately familiar with ScreamingMonkey as you are.) And I also said 2) in my opinion, ES4 VM compatibility with ES3 (in perf characteristics in particular, but I’m betting in other ways as well) will likely cause interop problems. I understand your ideal is that an ES4 VM ought to be able to run ES3 scripts; I expressed skepticism this will happen, given the scope of changes to the language in ES4. Again, my opinion.