Re: Apple is deprecating Java

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Sun, 24 Oct 2010 15:28:57 -0400

Message-ID:

<4cc488f3$0$23752$14726298@news.sunsite.dk>

On 24-10-2010 15:15, BGB / cr88192 wrote:

"Arne Vajh?j"<arne@vajhoej.dk> wrote in message
news:4cc38955$0$23765$14726298@news.sunsite.dk...

On 23-10-2010 01:23, BGB / cr88192 wrote:

"Arne Vajh?j"<arne@vajhoej.dk> wrote in message
news:4cc2160b$0$23763$14726298@news.sunsite.dk...

On 22-10-2010 03:48, BGB / cr88192 wrote:

JNI and JNA leave a bit to be desired...
having to use pre-existing classes or interfaces to interface Java with
anything else is... lame...

these are not unfixable problems, but thus far the major VM's have not
done
much to improve on them.

even CNI (like GCJ) would be an improvement (just better would be not
having
to use GCJ to use it...).
admittedly, this front is a little awkward...

but, I am left to wonder sometimes if the poor interface mechanisms are
maybe deliberate...

It has certainly had the effect that the usage of JNI is rare.

yes.

Sun devises nearly the worst possible way to interface between C and Java
and standardizes on it as a covert attempt to prevent people from
plugging
together C and Java code except in case of dire emergency...

I don't think SUN sees it as a problem.

And many Java developers neither.

We don't need this:
http://www.mono-project.com/MoMA

:-)

JNI is kind of lame when dealing with a largish mixed language codebase

Absolutely.

this is back to the whole "vision" thing.

Java was seen as a framework for creating and distributing
architecture-neutral apps...
to this extent, it works well enough...

Yes.

however:
totally left out of the mix is people who are mostly building C and C++
apps,

Yes.

I suspect probably Sun didn't really want people writing mixed apps, and
using Java as a scripting language, since this would hinder its use in the
above category (as an app-distribution platform).

Yes.

JNI seems to be designed in such a way to make this particular usage pattern
somewhat awkward (one has to use the JNIEnv pointers which are not
gueranteed to be valid if saved between calls, ...), and AFAIK there is no
external C-side API, ...

What is "external C-side API"?

JNI certainly contains API for C->Java.

but... not everyone wants or needs such a "platform".

True.

Arne