SI
SI
discoversearch

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 : MSFT Internet Explorer vs. NSCP Navigator

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Frodo Baxter who wrote (10591)6/29/1997 1:32:00 PM
From: Justin Banks   of 24154
 
JAVA VM Comparison Motivation : To test Lawrence claim that Microsoft Java VM is considerably faster without any standards-violating features.

Methodology : An analysis of what Lawrence knows was performed, and conclusions drawn based upon what he could possibly know.

Results : Because Lawrence hasn't seen the MSFT Java VM code, and MSFT hasn't released public specs, he cannot possibly know whether or not it violates parts or all of the Java standard. MSFT's source is not currently available, as they have not yet released it to Sun.
Claims that a 266Mhz processor is significantly less than twice as fast as a 166Mhz processor reveal either a complete misunderstanding of the non-linearity of processor speedup, an attempt at deliberate obfuscation, or both. The fact is that object code run on a 266Mhz processor would be significantly less than twice as object code on a 166Mhz processor under almost any circumstances.

Discussion : The methodology used by Mr. Kam to test whether MSFT Java VM implementation is 'better' is, to say the least, flawed. Using a Java test suite that contains *NO* implementation-specific optimizations is not a guarantee that the implementation in question will honor the standard, or even that the VM is actually executing the code. It is feasible that any given implementation could gain a speedup of several orders of magnitude by intentionally violating the standard. Without knowing details of the implementation, it is impossible to know whether or not that implementation violates the standard.

Conclusion : Mr. Kam has been 'Smokin!' a little too much of something, if he believes that this is conclusive evidence of Microsoft's adherence to the Java standard.

-justinb
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext