1
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
4
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5
<meta name="Author" content="Norris Boyd">
6
<meta name="GENERATOR" content="Mozilla/4.72 [en]C-NSCP (WinNT; U) [Netscape]">
7
<title>Rhino History</title>
11
<center><b><font size=+3>Rhino History</font></b></center>
13
<p>Rhino gets its name from the animal on the cover of the <a href="http://www.ora.com/">O'Reilly</a>
14
book about JavaScript.
15
<p>The Rhino project was started at Netscape in Fall 1997. At the time,
16
Netscape was planning to produce a version of Navigator written entirely
17
in Java and so it needed an implementation of JavaScript written in Java.
18
When Netscape stopped work on "Javagator", as it was called, somehow Rhino
19
escaped the axe (rumor had it that the executives "forgot" it existed).
20
Since then, a couple of major companies (including Sun) have licensed Rhino
21
for use in their products and paid Netscape to do so, allowing us to continue
22
work on it. Now Rhino is planned to be part of several server products
23
from Netscape as well.
24
<p>Originally, Rhino compiled all JavaScript code to Java bytecodes in
25
generated classfiles. This produced the best performance (often beating
26
the C implementation of JavaScript when run on a JIT), but suffered from
27
two faults. First, compilation time was long since generating Java bytecodes
28
and loading the generated classes was a heavyweight process. Also, the
29
implementation effectively leaked memory since most JVMs don't really collect
30
unused classes or the strings that are interned as a result of loading
32
<p>So in Fall of 1998, Rhino added an interpretive mode. The classfile
33
generation code was moved to an optional, dynamically-loaded package. Compilation
34
is faster and when scripts are no longer in use they can be collected like
35
any other Java object.
36
<p>Rhino was released to mozilla.org in April of 1998. Originally Rhino
37
classfile generation had been held back from release. However the licensees
38
of Rhino have now agreed to release all of Rhino to open source, including
39
class file generation. Since its release to open source, Rhino has found
40
a variety of <a href="users.html">uses</a> and an increasing
41
number of people have contributed to the code.
43
<hr WIDTH="100%"><a href="index.html">back to top</a>
1
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
4
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5
<meta name="Author" content="Norris Boyd">
6
<meta name="GENERATOR" content="Mozilla/4.72 [en]C-NSCP (WinNT; U) [Netscape]">
7
<title>Rhino History</title>
11
<center><b><font size=+3>Rhino History</font></b></center>
13
<p>Rhino gets its name from the animal on the cover of the <a href="http://www.ora.com/">O'Reilly</a>
14
book about JavaScript.
15
<p>The Rhino project was started at Netscape in Fall 1997. At the time,
16
Netscape was planning to produce a version of Navigator written entirely
17
in Java and so it needed an implementation of JavaScript written in Java.
18
When Netscape stopped work on "Javagator", as it was called, somehow Rhino
19
escaped the axe (rumor had it that the executives "forgot" it existed).
20
Since then, a couple of major companies (including Sun) have licensed Rhino
21
for use in their products and paid Netscape to do so, allowing us to continue
22
work on it. Now Rhino is planned to be part of several server products
23
from Netscape as well.
24
<p>Originally, Rhino compiled all JavaScript code to Java bytecodes in
25
generated classfiles. This produced the best performance (often beating
26
the C implementation of JavaScript when run on a JIT), but suffered from
27
two faults. First, compilation time was long since generating Java bytecodes
28
and loading the generated classes was a heavyweight process. Also, the
29
implementation effectively leaked memory since most JVMs don't really collect
30
unused classes or the strings that are interned as a result of loading
32
<p>So in Fall of 1998, Rhino added an interpretive mode. The classfile
33
generation code was moved to an optional, dynamically-loaded package. Compilation
34
is faster and when scripts are no longer in use they can be collected like
35
any other Java object.
36
<p>Rhino was released to mozilla.org in April of 1998. Originally Rhino
37
classfile generation had been held back from release. However the licensees
38
of Rhino have now agreed to release all of Rhino to open source, including
39
class file generation. Since its release to open source, Rhino has found
40
a variety of <a href="users.html">uses</a> and an increasing
41
number of people have contributed to the code.
43
<hr WIDTH="100%"><a href="index.html">back to top</a>
added
removed
docs/history.html
