Mostly I never understood the point of JIT in the .net framework. You pay a price in term of startup time, but the reality is that you can only run .net on x86 and x64. So we might as well have saved the trouble. And the first time .net was given an opportunity to run on ARM (WinRT), they disallowed regular .net applications in order to introduce a toll through the windows store.
We would have been better off without JIT. Even now with ARM. You compile to 3 architectures,... so what?
Re:Guide to the CoreCLR Source Code
by chrisseaton on Friday March 24, 2017 @04:55PM
(#13952158)
Normally I would argue that the point is that it allows speculative runtime optimisations, but .NET doesn't do that.
[dead]
Hmmm really? I'm not sure I can think of many technological breakthroughs in the area of JITs that Microsoft have been responsible for? Google and Mozilla have made lots of advances, as have Sun and Oracle, and lots of academics like the PyPy people, HP with Dynamo.
What have Microsoft done in the area of JITs that so notable as to earn them the title 'king' of JITs? Can you say anything specific?