| 1 |
Syracuse and Las Vegas Workshops saw no serious problem to High Performance Java on sequential or Shared Memory Machines
|
| 2 |
Some restrictions are needed in programming model
-
Cynic says write in Fortran with Curly Brackets but more seriously restrictions requires programming discipline but still exploit key advantages of Java
|
| 3 |
For instance, Avoid Complicated Exception handlers in areas compilers need to optimize!
|
| 4 |
Should be able to get comparable performance on compiled Java C and Fortran starting with either Java Language or JavaVM bytecodes
|
| 5 |
The Interpreted (Applet) JavaVM mode would always be slower than compiled Java/C/Fortran -- perhaps by a factor of two with best technology
|
