[NTLUG:Discuss] OT: Java question

[Stephen Davidson]

Greg Edwards wrote:
> Stephen Davidson wrote:
> 
>>
>> Today JVM - 1.4.2
>>
>> To install Modern JVM;
>> For IE - http://java.com - choose appropriate for your
>> system, should autoinstall modern plugin.
>>
>> For Mozilla - http://mozilla.org for instructions
> 
> 
>>
>> Regards,
>> Steve
>>
> 
> It was my understanding that M$ was going to discontinue support for 
> Java from any IE products and replace it .NET only support.  Anyone know 
> if this is still true?  Does this mean that they'll try to block Java as 
> a valid plugin?  Is Sun, or anyone else, planning on maintaining an M$ 
> version of JVM to fill the void if M$ drops it?
> 

Makers and Sellers of Java VMs for MS platforms;
Sun - Free to endusers & small software developers, $$ for some Developer Tools
IBM - Maker of Hotspot JVM & Jikes Technology - Contender for fastest JVM on the planet
BEA - I believe their JVM is called JRocket, the other contender for the fastest JVM on the planet

These are the best known, but not the only ones.  For instance, there are several real-time JVMs on the market (although I doubt they are MS based), 
embedded versions of Java, your cell phone has Java (I do not kid you, if it was made in the last two years, guaranteed, if older, still most likely 
does), your PDA probably has Java.  Blackberry was the first portable device to be sold with Java, but by no means is it the only one today.  And 
one of the real-time systems is handling the Fly-by-wire systems on various JetFighters.  Oh yeah, Java is also what lives on and run smart cards, 
at least the Army Tags, Amex Credit Cards, & Visa Credit Cards.

MS has tried to block Java installs on the Desktop in the past, and currently warn you during install that Java is "Unsecure".  While the MS version 
certainly is, no other manufacturer has had the JVM hacked, and there have yet to be Java virii.

And courtesy MS FUD, it is not generally known that as of JDK 1.3, Java has been running as fast as most well written C programs, and starting with 
1.4, it is starting to think about taking on Assembly (in some cases).  New to JDK 1.3 - JIT >>> Just In Time Compiler.  This little thingy lives in 
the Java Virtual Machine, and is tasked with compiling the Java Byte Codes down to the Native Machine code in an optimal fashion.  Basically, it is 
a Java Byte Code compiler, whose job is to optimize the compiled native machine to the current platform.  Slick, eh?  End result, Java 1.3 can hold 
its own against most C compiled software, and in some cases (ESPECIALLY THE Microsoft Visual compilers, any guesses why?  I don't know - seriously I 
don't), can beat code compiled with certain compilers.  This was found by an independent study.  Some Master's student working on his PHd wanted to 
know how much slower Java 1.3 was from C & C++. The answers surprised everybody.  Don't have the link right now, but if anybody really wants to 
know, I will chase it down.

New to JDK 1.4 (it was decided 1.3 was still too slow), the Runtime Profiler.  Again, this little beauty lives in the JVM.  What it does is sit 
there watching the code run, and figuring out how to make it run faster.  Generally waits until the block of code has been called about 50 times 
before it kicks in, then starts speeding it up.  Starts by pulling out redundant security and type checks, starts inlining calls, unrolling loops, 
that kind of thing.  A few papers have been written on this topic.

Bottom line, Java is not going anywhere.  MS managed to keep it off of the desktop, initially, so Java folks went and "conquered" the rest of the 
world.  We can honestly say that there are more than 1 Billion Java Deployments out there (I think its into the MultiBillion at this point, but not 
sure).  Now, having conquered (almost literally) the rest of the world, Java is coming back to the Desktop.  Dell, HP, & Compaq are now shipping Sun 
Java with their new machines, courtesy of several restraint orders on MS.

Hmmm, seem to have gotten on a soap box here.  Sorry for being so long winded, but ignorance on this topic only helps MS.

Regards,
Steve

-- 
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741