Differences between version 15 and predecessor to the previous major change of Java.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 15 | Last edited on Wednesday, November 19, 2003 6:46:16 pm | by AristotlePagaltzis | Revert |
Older page: | version 12 | Last edited on Sunday, October 26, 2003 7:54:23 am | by AristotlePagaltzis | Revert |
@@ -14,9 +14,9 @@
[Java] is an example of good object oriented design (generally). Almost all of [Java]'s internal classes are very well defined and all follow a nice naming convention.
[Java] applets allow [Java] programs to be written and run in [WebBrowser]s. Unfortunately, after [Java] 1.1, Microsoft didn't quite agree with [Sun] and stopped updating the version of [Java] that comes with InternetExplorer, the most common WebBrowser. Because of this, most applets you see on the internet today are limited to a very old version of [Java] and don't make use of all the new features in [Java] today (version 1.4.1 at the time of writing).
-[JavaBean
]s
allow dynamic introspection of software components and streaming of state-full objects across the network without full knowledge.
+[Java
]Beans
allow dynamic introspection of software components and streaming of state-full objects across the network without full knowledge.
!! Issues
But Java, like any ProgrammingLanguage, has cons. First, Java's Run-time Environment (JRE) is a big download and is needed for any user wishing to run a Java program. This JRE also incurs quite a large memory penalty, even running a simple application can take quite a large amount of memory.
@@ -32,11 +32,11 @@
The popular JREs start a new virtual machine for each java program, rather than sharing one amongst all programs. This combined with the large memory overhead can make it impractical on machines more than a few years old. (AddToMe - is this still true these days?)
The lack of a Free JRE (along with JRE size and speed issues) is probably one of the biggest obstacles to wide-spread adoption of Java on Linux. However, most of the issues mentioned above are implementation issues so could in theory be overcome. For example, the [GCC] project is part-way through a java compiler that would (of course) be licensed under the [GPL].
-See JavaNotes
+See JavaNotes, [JavaAndC++]
''Lots to be refactored here. AddToMe.''
----
-CategoryProgrammingLanguages, CategoryImperativeProgrammingLanguages, CategoryObjectOrientedProgrammingLanguages
+CategoryProgrammingLanguages, CategoryImperativeProgrammingLanguages, CategoryObjectOrientedProgrammingLanguages, CategoryMachineOrientedProgrammingLanguages