I'm curious about the ethics involved if one decided to omit some education from their CV. That is, what if you got the Ph.D. and didn't report it on your resume?
RDF is the Resource Description Framework, a W3C recommendation for making web content understandable by machines. Slashdot's own RDF is here. Cool, huh?!
As I recall, Raskin's original rift with the Macintosh developed because he wanted it to be an "information appliance." Except for the size and input dvice (i.e., no keyboard), seems to me like we have what he's been proposing all along, and it's called a Palm Pilot.
The Palm is a perfectly useful, wonderful device, but it isn't about to replace any of my desktop machines, or vice-versa.
Java's speed problems (including startup) are largely limited to 1.1.x VMs. The latest Java2 VMs, HotSpot for instance, only JIT frequently used code (lots o' calls, loops, accessors, etc.), so the startup is very fast -- the latest JITs even use templates like good C compilers have been for years to speed up the compile times.
As the applet/application runs, it gets faster due to dynamic optimization based on actual usage. The JIT can even make compiled copies of polymorphic methods (superclass and derived class) and call the appropriate one at runtime. These are things that C++ can't do because it's optimizer is static (pre-run), not dynamic (runtime).
Bottom line is that Java2 performance is as good as or better than C++.
So why's Java in trouble? Because MS controls IE, IE is the most widely used client-side Java platform (hate to say it, but it's true), and MS has prevented Java2 from getting into the browser, so you'll never see all the great performance unless you go to the trouble to install the plug-in.
Sad, but this is nothing new. MS is merely repeating the pattern of abuse that got them where they are today (and convicted of anti-competitive practices in a court of law).
My only hope is that Sun doesn't sit back and let MS kill Java on IE. If the default VM becomes "no VM" and we let MS win, we'll all be without Java on the client side for ever. Run a good swing app on a good Java2 VM and you'll see what you could be missing.
Slashdot Mirror
I'm curious about the ethics involved if one decided to omit some education from their CV. That is, what if you got the Ph.D. and didn't report it on your resume?
The G4 screams if you take advantage of AltiVec. Apple has some interesting pages on how to do so here.
RDF is the Resource Description Framework, a W3C recommendation for making web content understandable by machines. Slashdot's own RDF is here. Cool, huh?!
The Palm is a perfectly useful, wonderful device, but it isn't about to replace any of my desktop machines, or vice-versa.
As the applet/application runs, it gets faster due to dynamic optimization based on actual usage. The JIT can even make compiled copies of polymorphic methods (superclass and derived class) and call the appropriate one at runtime. These are things that C++ can't do because it's optimizer is static (pre-run), not dynamic (runtime).
Bottom line is that Java2 performance is as good as or better than C++.
So why's Java in trouble? Because MS controls IE, IE is the most widely used client-side Java platform (hate to say it, but it's true), and MS has prevented Java2 from getting into the browser, so you'll never see all the great performance unless you go to the trouble to install the plug-in.
Sad, but this is nothing new. MS is merely repeating the pattern of abuse that got them where they are today (and convicted of anti-competitive practices in a court of law).
My only hope is that Sun doesn't sit back and let MS kill Java on IE. If the default VM becomes "no VM" and we let MS win, we'll all be without Java on the client side for ever. Run a good swing app on a good Java2 VM and you'll see what you could be missing.