| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
You mean that Sun--the vendor and provider of the Java implementation in question--is *not* the final authority? Who would know better than Sun how Java behaves, and what correct practice is?
It is the *nonportable* program that requires that all platforms be identical.The Java VM is designed to behave identically on all platforms when executing bytecode. Still, this is a quotable expression in the tradition of "War is Peace. Freedom is Slavery". It is the deployment that is not yet portable enough. We must solve that by speaking out to Apple when there is something that is easy to solve.
Enterprise computing is mostly about compulsively backing up everything. It is also about designing *efficient* fallback and fallforward scenarios; some vendors do not cooperate.
Color me amazed! I never knew that "deployment logistics of enterprise computing" don't include making backups of critical files and systems before installing new software. Apparently, it's also the norm for enterprise computing to impulsively install every new release as soon as it comes out, without putting it through any sort of evaluation first or waiting to see whether anyone else encounters problems. (I'd think that a business that depended on computers for its livelihood would take greater care, but apparently not.)
Enterprise computing also routinely uses for production work software that is explicitly stated not to be suitable for production work. The things I never knew!
Like I said, that is only bad for Apple, and only when it does want this market. The graphical people appararently first seem to wait years for Quark and then still want to be their customer. I can tell you that this is a different world.
| Most of the time, the operational department has to support as many VM versions
| on a machine as there are (sometimes contractual) requirements from the applications.
| This is not possible on Mac, and that is a pity.
Why not? Can't the contracts be renegotiated? And what do you do about versions of the JVM that never existed on the Mac? (There is, for instance, *no* Java 1.4.0 for the Mac. Apple went directly from 1.3.1 to 1.4.1.)
Anyone ill-informed or unthinking enough to conclude that the entire OS is worthless because *one program* has problems is likely to give up on OS X because it's not Windows.And we would not want those people as customers running on XServes if we were Apple, wouldn't we? Even if that *one program* is their 45 million dollar in-house system?
Overall, your argument boils down to "developers shouldn't have to modify their programs as a result of platform vendor changes". Unfortunately, change is inevitable. The *successful* developers will be those that *do* the modifications; the *unsuccessful* ones will be those that insist that the platform vendors guarantee compatibility with all previous releases.
| References: | |
| >Re: Using Lomboz plugin with Eclipse (From: Greg Guerin <email@hidden>) | |
| >Re: Using Lomboz plugin with Eclipse (From: René Jansen <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.