You're misrepresenting what apple is doing (or misunderstanding). Apple isn't trying to bash java - they are trying to force all apps seen by apple consumers to be either vanilla web OR apple-controlled CoreX/Cocoa. client-side Java is just one of the many casualties of this process, but server-side java hasn't _AT ALL_ been affected by this move, because it doesn't impact Apple's plan to force all apple consumer client-side run stuff to be web or CoreX/Cocoa. In fact, it got better, because this move should streamline JVMs across platforms.
So, to reiterate: 1. Apple is not just bashing java, as they are clearly also bashing flash/AIR and silverlight. 2. Apple is not bashing java, they are actually bashing swing/awt. On Oct 27, 4:42 pm, Casper Bang <[email protected]> wrote: > Well let's see... the deprecation of Cocoa bindings + the lack of Java > on iDevices + refusal to accept Java apps through Mac app store + > deprecation of Mac JRE? Call me a conspiracy theorist, but I sence a > common theme here and a likely end game. > > On Oct 27, 11:16 am, Reinier Zwitserloot <[email protected]> wrote: > > > > > > > > > Apparent? From what? > > > On Oct 27, 8:59 am, Casper Bang <[email protected]> wrote: > > > > Except, it seems apparent that Apple wants to banish all Java! So to > > > claim that they are only deprecating Swing/AWT is a bit of a Cumbayá > > > twist. > > > > > In a sense, one could say that Apple hasn't "deprecated Java" at > > > > all... just Swing/AWT. -- 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.
