David Rocks wrote:
| I know there has been a lot flying by, but how do I tell Apple they
| shouldn't wait until tiger is released.
Find one of the official e-mail addresses for such things on the Apple web site, and use it. But, when you do, remember that Apple does things as Apple sees fit, and generally ignores outside opinion. And, if Java 1.5 requires 10.4, as is speculated, 1.5 *can't* come out before 10.4.
| There are already eclipse
| projects that require 1.5
And why exactly should Apple care about that? Or let it influence the schedule they've already established?
| [Apple] will have to put it on panther anyways
Why? Who's going to make them? It's in Apple's interest *not* to put it onto Panther. Apple makes money from OS upgrades; they don't make money from Java upgrades. (Popular myth is that Apple is a charity, and will do things that don't benefit Apple so that other parties *will* benefit. Reality is that Apple is a business, and does things that benefit Apple even if those things harm other parties.)
| because not everyone is going to switch
Apple: "We support only the currently-shipping version of the OS." Such people are, by choice, abandoning Apple support.
| and their are a lot of companies more
| concerned about development costs and schedules than core OS upgrades.
Companies concerned about development costs probably shouldn't be diving into Java 1.5 immediately. Every new major Java release has brought with it non-trivial bugs; a prudent company will let *other people* find those bugs, rather than spend development effort finding the bugs themselves. Staying with the older version will allow postponement of training, and of the acquisition of new versions of tools, both of which reduce [immediate] costs. It will also keep the customer base as large as possible, maximizing the potential income to the company.
Aside from that, this seems to be another round of developers whose plans require that their customers upgrade to the latest version of Java complaining that Apple's plans require that *they* upgrade the OS to the latest version. I've never understood that argument. If making new software work on older versions is a Good Thing, why isn't it a Good Thing for developers, too? But a developer who's actively supporting pre-1.5 versions will probably find it simpler to do most development on 1.4 (if not 1.3), to make it harder for 1.5-isms to sneak into the code, and will therefore not be in any hurry to make 1.5 the default version.
Glen Fisher
_______________________________________________
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
