humm, the problem is... Java is pretty much used for development tools for Java projects or for Java projects of which the bulk of those are enterprise apps. Objective-C will not replace nor will apple hardware replace what's being used in the enterprise environment. And, most enterprises don't care about using Mac hardware for the development of enterprise applications. Windows is good enough... so I don't see pressure here from that direction. The pressure is; Java is now dead on emerging client platforms. The only hope is that Oracle and Google settle in a way that keeps Dalvik going. If not, Android will live on without it and that will be it for java on client platforms... outside of enterprise applications. And that won't most likely include a whole lot of end user GUIs.. I suspect the bulk will be operational interfaces.
Kirk On Oct 23, 2010, at 11:51 AM, Chris Adamson wrote: > On Oct 22, 6:17 pm, Rob Ross <[email protected]> wrote: >> What kind of crazy logic is this, to blame Oracle because *Apple* is >> deprecating their JDK? Are you saying Sun/Oracle should be maintaining a >> separate port of the JDK for every vendor that does one of their own??? > > If the value provided by Java isn't enough to make it worth a platform > vendor's time and money to maintain a Java port -- which is apparently > where we now stand on OS X -- then the ball is in Oracle's court. > There are several reasons it would be in Oracle's self-interest to > provide Java for OS X: > > * It will keep Java attractive to developers. Without Java on Mac, > some number of developers will stop developing Java, and others in the > future who would have developed Java won't, solely because it isn't > available on their platform of choice. It is impossible to know how > big or small this number is. > > * It will maintain Java's perceived legitimacy. Given the order-of- > magnitude division of desktop market share (it's not too far off to > round it to 90% Windows, 9% Mac, 0.9% Linux), not being on Mac > effectively makes Desktop Java a Windows-only technology… which is of > course completely pointless, because at that point, you might as well > just write native Windows apps. > > The underlying story here, IMHO, is the final and total failure of > Desktop Java. If it mattered, Apple couldn't afford not to support > it, because there would be a class of users other than Java Developers > who would miss it, and wouldn't buy Macs because of its absence. That > failure really is Sun's fault, and therefore Oracle's problem to fix, > should it choose to. > > --Chris > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
