language interpreters/ interpreted languages weaknesses?

[Blake Winton]

On Thu, 2 Sep 1999 18:40:41 GMT, Paul Prescod wrote:
>David Oppenheimer wrote:
>> I am sure that many of you can relate to having run into a page where
>> a Java applet is loading and been quite irritated that while this
>> Java code is loading (being interpreted or the JVM is firing up or
>> whatever) that your browser (and your cursor too) will lock-up until
>> the applet is ready to run.  
>There are by now dozens of impementations of Java and your complaint is
>with a single one (or maybe two, if you have had the same problem with
>Internet Explorer and Netscape). Seriously this has nothing to do with
>Java *the language*. A bad implementation of Python could do the same
>thing.

Which points out, IMHO, Java's biggest problem.
There is no distinction between Java *the language*, Java *the VM*, Java
*the OS*, etc...  When my MSVC++ program is slow, I know enough to blame
the MFC, and not C++ the language, but with Java the distinction is
blurred (purposely, by Sun, it seems).

Of course, this has nothing to do with Python, except possibly to warn
Python to stay out of that trap.

Later,
Blake.

-- 
One Will.  One Dream.  One Truth.  One Destiny.  One Love.