Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Siebel Systems (SEBL) - strong buy? -- Ignore unavailable to you. Want to Upgrade?

To: ahhaha who wrote (6495)	10/24/2002 1:47:33 AM
From: Hardly B. Solipsist	Respond to of 6974

I'm aware of all this. It does make a difference, but the difference is not entirely in favor of the approach that Microsoft has taken. Doing some interpretation before compilation can allow the compiler to make optimizations that are not apparent from static analysis (that is, if you collect data that tells you that only certain use is being made of the code you can generate code that is slanted in favor of that specific use). On the other hand, for large applications having to run the JIT to get things compiled can be a non-trivial overhead. (Running only compiled code in a system like this was first done, as far as I know, in the ParcPlace Smalltalk system -- Peter Deutsch wrote a very clever and highly portable JIT that was good enough that they got rid of their interpreter.) I think that the .NET engine is very good -- the people that developed it are really first-rate, and if I had to choose which approach is best, I'd vote in favor of theirs. But in practice the performance of the JDK is very good, and I don't think that any difference is enough to affect which one to choose. The choice seems to me to be more geopolitical than technical. I also believe that there is enough momentum behind J2EE that even if Sun goes away eventually, the reference implementation will survive.