>> in your previous post you said,
>> "Oracle is betting on ORACLE'S Java, by the way, not anyone
>> else's. "
That had to do with performance concerns. It would be like people
worrying about C performance (which they did at the beginning) by
pointing out lousy C compilers and saying "See, it's too
slow". Oracle needs Java standards, and if all Java VM's stink
then that won't help, but it remains usable for Oracle customers
if Oracle's Java performance is okay.
>You seem to have changed your tone in the post I'm responding
>to. You'd like to see JAVA standards as open. I agree. It
>has to be otherwise nobody will use it, IMO. And ORACLE is
>not going to write all the JAVA applications needed for it.
There are already a lot of Java applications. There are also
about a 100,000 PL/SQL programmers in the world, and that is an
Oracle-only language. So Java could fail completely and still be
used by a lot of people. And it won't -- there will be a lot of
people writing Java applications for Oracle outside of the
company.
>>So it's true that Oracle is betting heavily (although not
>>exclusively) on Java, but it's also true that this bet will
>>win.
>Well, what if the bet doesn't work out? Does Oracle have
>a back door? Or a Plan B? Java still has a ways to go, it
>seems to me, to be accepted by most of the software community.
Well, what if an asteroid hits the planet and we all die? I've
heard Ellison say that he doesn't like to deal with hypothetical
questions, and I have to agree with him. It isn't going to
happen. Now I really don't know what Oracle is going to do, but
I'm sure that if you don't want to use Java that won't stop you
from using Oracle's products. And I'm also sure that Oracle will
be writing lots of new stuff in Java because it will be faster
and more reliable and conform to standards better.
|
