On JavaScript performance in IE8

re: On JavaScript performance in IE8

int19h — Fri, 26 Sep 2008 16:57:51 GMT

Come to think of it, why not just use JScript.NET to compile to CIL, and then the .NET JIT compiler? Both are mature, stable solutions, and from what I've seen about JS.NET, it covers the entire ES-262 subset, so what else is needed? It would also fit nicely with Silverlight 2.0 in the future - if both JS scripts on the page, and Silverlight code-behind, run on .NET, it would provide for some interesting interop scenarios...

re: On JavaScript performance in IE8

Ian M — Thu, 30 Oct 2008 14:16:06 GMT

Why not just adopt V8? It's BSD licensed.

re: On JavaScript performance in IE8

Joel Coehoorn — Thu, 21 May 2009 17:58:51 GMT

> Why not just adopt V8? It's BSD licensed.

Because that would have three important negative implications:

1. They'd need to fork the V8 engine completely, so they can make it compatible with their existing render engine, DOM, and security model. This works isn't exactly trivial either, and what you have is a whole new animal (it's not _really_ V8 any more). The political implications of this are also important. Can you image the outrage if MS "stole" V8?

2. After all that's done, not only are they still dependent on the V8 team to some extent for bug fixes and security updates, but their ability to continue to innovate is either limited to what the V8 team is willing to do or they have to ignore any changes made to V8 completely.

3. It's very possible they have other technology licensed for use with IE that would limit their ability to just add any open source code they want.