Yeah, I don't seem to recall Apple keeping their Objective-C 2.0 plans
or Dashcode a super-secret up until release. The SOP excuse doesn't
fly when you take that all into account, in addition to what you said.
On 17-Dec-07, at 12:32 PM, Joshua Portway wrote:
Alexei -
We aren't screaming "I want it now" (at least I'm not). I'm saying
"tell us what's going on".
And not speaking about unreleased products is one thing when it's a
new iThing that has been secretly developed in the underground
volcano laboratories of Apple. In that case you don't talk about it
because you want to be able to make changes to it, you might abandon
the idea completely, you don't want to pre-empt the marketing etc.
etc. It's quite another thing when you're talking about something
like Java 6 - everyone already knows what it's supposed to be like,
it's not even really a new product - everyone has seen it before on
Windows and Linux for over a year, Apple even had the beta on their
developer site for everyone to download for quite a long time
(before it disappeared without trace). There is nothing here to
keep secret, except the mystery of the disappearance itself. Java 6
is not a secret product - it's been talked about in the past by
Apple - why can they suddenly not talk about it now ? How could
reassuring people that it's still in development be detrimental to
Apple in any way ? Don't you think that someone, somewhere might
think that even a quiet word of explanation might be a good idea ?
There are teams of people now working on building their own
distributions of Java 6 for OSX - if Apple are still working on
their own version then don't you think they should mention it, for
the sake of avoiding any potential fragmentation of the platform if
not for the simple decency of sparing everyone from wasting all that
work.
Josh
On 17 Dec 2007, at 18:11, Alexei Svitkine wrote:
It would only benefit Apple to do this anyways, since they would
no longer have to maintain the JDK, and all the Apple Java
Development community will be the better for it. It would be win-
win for everyone.
And the existing Apple Java team should just be fired? Doesn't seem
like a "benefit for everyone".
I am confident that Apple is still working on Java 6, and the
reason it's not out, is because it's not ready. A million people
screaming "we want it now" won't magically fix the bugs and other
issues that are holding it back. I see no reason that Java 6 would
have been canceled, given that they've already had a working
prototype of it in the developer preview.
And I bet even the managers of the Java team can't authorize the
disclosure of the status of Java 6, since the "don't speak about
unreleased products unless you're Steve Jobs" policy is most likely
outside of their control.
-Alexei Svitkine
Fizzysoft
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Mike Brock
Senior Software Engineer
Red Hat, Inc. (JBoss Division)
email@hidden
CONFIDENTIALITY NOTE: This message is intended only for the designated
recipient(s). It may contain confidential or proprietary information
or other confidentiality protections. If you are not a designated
recipient, you may not review, copy or distribute this message. If you
receive this in error, please notify the sender by reply e-mail and
delete this message. Thank you.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
