3 ms·
I sincerely hope that they're using the JIT from .NET for this, although I've not seen .NET so much as mentioned anywhere near it. They already have a high-qua
by daeken 17y ago
I sincerely hope that they're using the JIT from .NET for this, although I've not seen .NET so much as mentioned anywhere near it. They already have a high-quality compiler that can emit insanely fast dynamic code, why not use it? Although honestly, I'd take it one step further: start rewriting everything possible in .NET, and improve the compiler in parallel (although they're obviously already doing this -- they're making good strides).
If you limit the portions that are in unmanaged code to the absolute most performance critical components, you could honestly tout it as the most secure browser. Not to mention the benefits of their generational GC, or the development time improvements. If they could cut their development and debugging time in half, they could potentially build a browser that actually doesn't suck (which, sadly, I don't believe exists from anyone right now).
- ZeroGravitas 17y agoThe latest comment from 'ieblog' says that it's not the same code, though some of the same folk worked on it.