Compiling is faster and when scripts are no longer in use they can be collected like any other Java object. The classfile generation code was moved to an optional, dynamically loaded package. (This has changed in later versions of Java.)Īs a result, in the fall of 1998, Rhino added an interpretive mode. Also, the implementation effectively leaked memory since most Java virtual machines (JVM) didn't collect unused classes or the strings that are interned as a result of loading a class file.
First, compiling time was long since generating bytecode and loading the generated classes was a resource-intensive process. This produced the best performance, often beating the C++ implementation of JavaScript run with just-in-time compilation (JIT), but suffered from two faults. Originally, Rhino compiled all JavaScript code to Java bytecode in generated Java class files. Since then, a couple of major companies (including Sun Microsystems) have licensed Rhino for use in their products and paid Netscape to do so, allowing work to continue on it. When Netscape stopped work on Javagator, as it was called, the Rhino project was finished as a JavaScript engine.
At the time, Netscape was planning to produce a version of Netscape Navigator written fully in Java and so it needed an implementation of JavaScript written in Java. The Rhino project was started at Netscape in 1997.
0 kommentar(er)
