【徹底討論】Java３Dの可能性について考える

【徹底討論】Java３D� ..

■コピペモード
□スレを通常表示
□オプションモード
□このｽﾚｯﾄﾞのURL
■項目テキスト

552:デフォルトの名無しさん
 04/10/17 23:26:28
This explanation is equally unsatisfying, because C++ and other languages have similar  
"abstraction penalties". For example, The Kernighan and Pike book The Practice of Programming  
has a table with the following entries, describing the performance of several implementations of a text processing program: 
 
 
    * 
 
      Another evidently well known problem in C++ is the overhead of returning an object from  
a function (several unnecessary object create/copy/destruct cycles are involved). 
    * Java program startup is slow. As a java program starts, it unzips the java libraries and  
compiles parts of itself, so an interactive program can be sluggish for the first couple seconds of use. 
 
      This approaches being a reasonable explanation for the speed myth. But while it might explain  
user's impressions, it does not explain why many programmers (who can easily understand the idea  
of an interpreted program being compiled) share the belief.  
 
Two of the most interesting observations regarding this issue are that: 
 
   1. there is a similar "garbage collection is slow" myth that persists despite decades of evidence  
to the contrary, and 
   2. that in web flame wars, people are happy to discuss their speed impressions for many pages  
without ever referring to actual data.

次ページ