It's interpreted byte code. That can't compete with compiled machine code. Like the original idea behind Java (ie: write once run anywhere, not compiled Java). Anyone care to make a similar test in Java?

But calls to native Director methods (imaging Lingo calls, for instance) are machine compiled code, so those run full-speed.

-Daniel

Tim Welford wrote:
So, after more than 10 versions, does anybody have any idea why the
backend is still so inefficient?

[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]

Reply via email to