Regarding the JIT...
I saw an article on the net sometime ago, from an engineer who works on .NET. ( no link sorry )
From what I remember:
-the runtime looks at the size of your cpu cache
-it can emit different code depending on whether its amd or intel, and what model it is.
-there is more room for cpu specific tuning, but theres the issue of diminishing returns/harder to track customer issues resulting from extra codepaths, etc.
Also like someone mentioned, some versions of java can profile code as it runs, and optimize certain hotspots of execution...
So thats the good stuff. But rico mariani, says straight out, the current .NET JIT has to run fast, so it can't do all the analysis a good static compiler can. But it does a very good job considering. Paraphrasing him, he said think of the JIT as a fixed, but tiny overhead. ( http://blogs.msdn.com/ricom/archive/2006/08/22/713396.aspx )
At the end of the day, you still get pretty good codegen tailored to your system-- combined with fast memory allocation, and good locality of cache. End result is pretty speedy programs.
I can't speak for java, but in my somewhat limited testing , c# almost always beats b3d/b+ in a big way. Haven't bothered testing with blitzmax.
There's a decent amount of info on the web regarding JIT advantages. I think IBM's website has some good papers on it.
I saw an article on the net sometime ago, from an engineer who works on .NET. ( no link sorry )
From what I remember:
-the runtime looks at the size of your cpu cache
-it can emit different code depending on whether its amd or intel, and what model it is.
-there is more room for cpu specific tuning, but theres the issue of diminishing returns/harder to track customer issues resulting from extra codepaths, etc.
Also like someone mentioned, some versions of java can profile code as it runs, and optimize certain hotspots of execution...
So thats the good stuff. But rico mariani, says straight out, the current .NET JIT has to run fast, so it can't do all the analysis a good static compiler can. But it does a very good job considering. Paraphrasing him, he said think of the JIT as a fixed, but tiny overhead. ( http://blogs.msdn.com/ricom/archive/2006/08/22/713396.aspx )
At the end of the day, you still get pretty good codegen tailored to your system-- combined with fast memory allocation, and good locality of cache. End result is pretty speedy programs.
I can't speak for java, but in my somewhat limited testing , c# almost always beats b3d/b+ in a big way. Haven't bothered testing with blitzmax.
There's a decent amount of info on the web regarding JIT advantages. I think IBM's website has some good papers on it.