Oglesby, David (MN65) wrote:
-----Original Message-----
From:
java-dev-bounces+david.oglesby=email@hidden
[mailto:java-dev-bounces+david.oglesby=email@hidden
le.com] On Behalf Of Ken
Sent: Tuesday, October 05, 2004 9:43 AM
To: email@hidden
Cc: email@hidden
Subject: Re: What in 1.5 is non-Java?
[...]
I truly regard Apples lack of commitment to providing newer JVM
availability, for their older OSs, as a greedy sales
motivator (not just
in java APIs either, sorry to say)and/or being due to lack of
programmer
resources. Making the 1.5(5) jvm only available for Panther
is just bad
for the community, becasue it produces as many compatibility problems
as, say, using native code would. Sad.
You mean Tiger, right?
Whoops, right. Jaguar wont be supported. Only Tiger will. My apologies
to the list.
<rant>
I am so tired of these arguments. Everyone sees his/her situation as the one
Apple should focus on. The simple fact is that not all java developers moved
to 1.5 the day it was released. Hell, there are people on this list
developing for Mac OS 9! Where do you get off demanding that Apple support
you as though you are the entire developer contingent they have to support?
You're tired of these argument, but you took the bait... No, clearly,
providing support to the widest community is in everyone's best
interest, not just mine. (true|false) And, YES, that includes
benefiting me, both as the apps user and developer. On the other hand,
mediocre cross-compatibility is EXACTLY what has time and time again
put companies on the brink of extinction (true|false).
Based on your statement below, you appear to be condoning that people
not write 1.5 apps, unless they expect any customer to who wants to run
them to buy an entire operating system upgrade. If this were sun's
strategy, java would almost certainly not exist right now - its primary
advantage of being non-platform-binding is its primary attribute that
shields it from being just another language like, say, VB.
Why does Apple have to support a lame duck operating system if you don't?
Not sure where you got that, but I am arguing for an environment that
supports the widest array of OSs... not the least of which is the one
that supersedes Tiger. Heck, its barely even two years old. You seem to
be the one labeling Panther as a lame-duck already, as justification
for it not having 1.5 available to it. Sheesh. That's extreme to me.
You don't expect Java 1.5 support for 10.1 do you?
ABSOLUTELY, unequivocally, YES!!!! :-) Not even the *slightest*
hesitance to say that. None.
Everyone is so quick to
tell Apple what they "must" do and accuse them of "greedy" tactics. Apple
has a responsibility to millions of users to protect the investment they
have made in the Macintosh platform. Has it occurred to you that there is
nothing greedy about saying they can't afford to develop and maintain Java
1.5 on two platforms? That isn't greed, it's strategic allocation of
resources.
Youre right here. As you imply, its a business strategy; a risk. "Do we
produce an environment that insures consistent experience to legacy
application users, and thereby possibly raise the community's regard
for our products, or do we make people upgrade to get the latest
features and guarantee revenue, at least in the immediate term, and
hope people dont mind it?"
</rant>
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
|
