The HotJava VM has received an official "End of Life" notice from Sun; its technology is incorporated into the current "client" and "server" VMs (so I'm told).
Again, this is simply not true.
The "client" and "server" compilers are both part of the HotSpot VM. (There's no such thing as "HotJava".) So HotSpot encompasses both compilers. Sun did not abandon its HotSpot team/work, trust sme. They're still going strong.
First off, I have interned three times at Sun, working on virtual machines. So I know a fair bit about VM's, and their run-time and processor-specific optimizations.
"it has always been clear that Java is inferior to native code applications in terms of raw power. Computational performance depends on the effective use of a target processor's instruction set; such optimization can not be expected of Java given its goals of universality and portability."
This statement is simply not true! The portability nature of Java does not conflict with a virtual machine that does processor-specific optimizations. Take a look at Sun's HotSpot VM source code (it's publicly available!) In the IA32-specific code, you'll see lots of run-time switches to enable specific P4 optimizations, for example.
"Perhaps Java's Just-in-Time compiler could be enhanced to perform processor-specific run-time optimizations; on the other hand, doing so would require different JVMs (Java Virtual Machines) for different architectures, or a single bloated JVM with run-time architecture detection."
This already exists in the current HotSpot VM. There's an IA32 binary, which includes optimizations for several versions of IA32. It does not include PowerPC or SPARC code, as that's in a different binary.
" The "ia32" world is already fragmented between Pentium III, Pentium IV, Itanium, Athlon, and Opteron architectures, each having unique requirements for optimization;"
That's the challenges a VM writer has to deal with. And the HotSpot team did a great job in managing this complexity.
In the future, if you (or anyone else, for the matter) takes the time to write a paper, you should do more research. Some of the statements above are simply misleading.
Prolog sucks! We're using it in university right now (University of Waterloo, Computer Engineering) for a few assignments. Now, this is not a typical "language X sucks because I don't really know it" rant! I would have much rather be doing some of the assignments in Lisp, which I know and enjoy! Shame on you, comparing Lisp and Prolog!
i didn't really watch the oscars, but i saw a five minute clip. and a really strange thing happened: when they were announcing the nominees, we heard "not this one" being quitely said for the first 4 nominees, and then "this is the one" for the last nominee, and it won! is this some kind of prank? did anybody hear this, and if so, was it repeated again?
Slashdot Mirror
Again, this is simply not true.
The "client" and "server" compilers are both part of the HotSpot VM. (There's no such thing as "HotJava".) So HotSpot encompasses both compilers. Sun did not abandon its HotSpot team/work, trust sme. They're still going strong.
"it has always been clear that Java is inferior to native code applications in terms of raw power. Computational performance depends on the effective use of a target processor's instruction set; such optimization can not be expected of Java given its goals of universality and portability."
This statement is simply not true! The portability nature of Java does not conflict with a virtual machine that does processor-specific optimizations. Take a look at Sun's HotSpot VM source code (it's publicly available!) In the IA32-specific code, you'll see lots of run-time switches to enable specific P4 optimizations, for example.
"Perhaps Java's Just-in-Time compiler could be enhanced to perform processor-specific run-time optimizations; on the other hand, doing so would require different JVMs (Java Virtual Machines) for different architectures, or a single bloated JVM with run-time architecture detection."
This already exists in the current HotSpot VM. There's an IA32 binary, which includes optimizations for several versions of IA32. It does not include PowerPC or SPARC code, as that's in a different binary.
" The "ia32" world is already fragmented between Pentium III, Pentium IV, Itanium, Athlon, and Opteron architectures, each having unique requirements for optimization;"
That's the challenges a VM writer has to deal with. And the HotSpot team did a great job in managing this complexity.
In the future, if you (or anyone else, for the matter) takes the time to write a paper, you should do more research. Some of the statements above are simply misleading.
Prolog sucks! We're using it in university right now (University of Waterloo, Computer Engineering) for a few assignments. Now, this is not a typical "language X sucks because I don't really know it" rant! I would have much rather be doing some of the assignments in Lisp, which I know and enjoy!
Shame on you, comparing Lisp and Prolog!
i didn't really watch the oscars, but i saw a five minute clip. and a really strange thing happened:
when they were announcing the nominees, we heard "not this one" being quitely said for the first 4 nominees, and then "this is the one" for the last nominee, and it won!
is this some kind of prank? did anybody hear this, and if so, was it repeated again?
Actually, the professional edition comes with Paradox, Corel's RDBMS