Spoken like someone who does not have a clue. Java is going to be in a application you use.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Discontinuing Java Installation Packages for Mac OS X?
- Thread starter MacRumors
- Start date
- Sort by reaction score
Spoken like someone who does not have a clue. Java is going to be in a application you use.
What would be the point? Java is pretty much dead on the client side.
If it were Sun I'd agree with you but Oracle is an unknown quantity and it's clear they see things very differently that Sun. Then again, I'm just being the devil's advocate here. I really really hope Oracle will do so.
That's what I am afraid of too.
Oracle does not have a big incentive to develop an OS X JVM. Like you mention Java on desktop is not a big market and OS X as an enterprise server is irrelevant. Also all enterprise java servers like Weblogic, Websphere... are not supported on the mac so Oracle might just decide to ignore the OS X platform for Java.
That's too bad as I would be forced to go to Linux or Windows as a dev environment if that happens.
Financial markets also use a lot of Java (even on the client-side)
Interesting - there is aso another Java app segment that Apple is forgetting about ... lots and lots of the brokerages and financial companies, like ETrade, use client-side Java. Most of these will simply continue to deliver in their app in Java.
Interesting - there is aso another Java app segment that Apple is forgetting about ... lots and lots of the brokerages and financial companies, like ETrade, use client-side Java. Most of these will simply continue to deliver in their app in Java.
Sorry to add little (I kind posted similar in another thread), but I am in agreement with many here.
Apple did a horrible job keeping their JVM up-to-date. I highly doubt that the Java on MacOS X will completely disappear. Oracle or another group of people will work on getting the JVM running. If there is a great enough need, there will be a solution. It may not be optimal, but it should be good enough for client-end runtimes.
As for the developers complaining that they bought their Macs for nothing. I don't know what you were doing developing Java on Mac OS X anyways. As stated earlier, Apple has always been very slow with Java updates and bug fixes all the way back since I can remember. You were being a glutton for punishment if you ask me.
Apple did a horrible job keeping their JVM up-to-date. I highly doubt that the Java on MacOS X will completely disappear. Oracle or another group of people will work on getting the JVM running. If there is a great enough need, there will be a solution. It may not be optimal, but it should be good enough for client-end runtimes.
As for the developers complaining that they bought their Macs for nothing. I don't know what you were doing developing Java on Mac OS X anyways. As stated earlier, Apple has always been very slow with Java updates and bug fixes all the way back since I can remember. You were being a glutton for punishment if you ask me.
I didn't know CyberDuck was Java based. I also use Oracle SQL Developer, another Java app.
I really hope it's because Oracle is committing to doing their own Mac OS X releases in a timely manner. I wonder what will happen to the Java Mac OS X native APIs though...
You won't be forced to do anything. What are you talking about?
Just because Apple won't be distributing Java apps in their new store, doesn't mean you can't use all your current distribution methods for delivering you software.
You post strikes me as one of those jump-the-gun comments because you didn't read the article.
I agree with the many people saying Oracle will support this but I think this shows that Apple has for years been negligent. Seems Apple wants to completely segregate themselves. I don't blame them however its a slippery slope.
Ridiculous statement. I'd like to see you back this up. I've been a professional Java developer for 10 years - over 5 years developing exclusively on the Mac. I can't think of a single issue I've ever had that I could point to the Apple version of the JVM. And it's not just me, it's dozens of Mac using co-workers.
I can think of maybe a single minor issue with a Linux version of the VM, that had a simple workaround. Java as a platform in general is simply not defined by its bugs.
I find this move strange, as it was my understanding that this latest Java update has quite a few new OS X specific feature enhancements. It seemed like quite a bit was getting done by their Java team behind the scenes.
While Apple was always a little behind version-wise, their Java team by-far did the best providing tools/APIs to integrate Java nicely with the OS X Desktop compared to other systems. Despite some of the complaints here, if a developer chose to do so, it has been very easy on OS X to create a Java application that is virtually indistinguishable from native applications.
While Apple was always a little behind version-wise, their Java team by-far did the best providing tools/APIs to integrate Java nicely with the OS X Desktop compared to other systems. Despite some of the complaints here, if a developer chose to do so, it has been very easy on OS X to create a Java application that is virtually indistinguishable from native applications.
We use VMs heavily to quickly switch between a large number of environments. It eliminates a lot of overhead for us; setting up a Mac Java development environment once is trivial, and the amount of times we update that pales in comparison.
You clearly did not read the article. This is about Apple possibly discontinuing distribution of the Java runtime for Mac OS X, not about Apple refusing to distribute Java apps in the Mac App Store.
Some years ago Apple started courting the Java community heavily and some people believed them (which was silly, of course). Personally, I bought into OS X after Apple changed their minds and I don't really have a problem developing on Linux instead. I just like OS X, is all.
Java != Javascript
Superficially, they appear to share some very vague syntactic similarities, and they share a similar-sounding name because of some silly marketing decisions at Netscape back way back when. (In fact, many moons ago, Microsoft changed the name of its implementation of Javascript to "JScript" specifically to avoid stepping on Sun's trademark of the word "Java".)
But in many much more important areas, Java and Javascript are as different as night and day.
Javascript is a core technology at the heart of Web 2.0, Ajax, and all those other buzzwords. Apple is an enthusiastic supporter of those technologies. Don't worry: Javascript isn't going anywhere.
iTunes stores runs on WebObjects, which heavily uses Java. So Apple must have already made arrangement with Oracle to supply the JVM.
People are just crying river over nothing. Apple wants to maintain only their own software now onwards, and doesn't want to develop third party software.
You guys should go back to old days where we had IE for Mac from Microsoft, which they stopped making and Apple had no option other than to come up with WebKit which powers Safari, Chrome and others (Nokia browsers). The biggest loser of this was obviously MS, IE's market share is all time low.
So Apple wants to support their platform, and if Oracle thinks OS X Platform is that important, they will maintain their software, Java, on Mac OS X Platform.
People are just crying river over nothing. Apple wants to maintain only their own software now onwards, and doesn't want to develop third party software.
You guys should go back to old days where we had IE for Mac from Microsoft, which they stopped making and Apple had no option other than to come up with WebKit which powers Safari, Chrome and others (Nokia browsers). The biggest loser of this was obviously MS, IE's market share is all time low.
So Apple wants to support their platform, and if Oracle thinks OS X Platform is that important, they will maintain their software, Java, on Mac OS X Platform.
LOL! They did say so! They documented it as deprecated code! It was Teh Epic Fail! crowd that blew it up into this huge ZOMG!!1! issue.
LOL! They did say so! They documented it as deprecated code! It was Teh Epic Fail! crowd that blew it up into this huge ZOMG!!1! issue.
Thats how I read it as well. Deprecated code means, something else is replacing it soon/next version of OS, from Oracle obviously.
LOL! They did say so! They documented it as deprecated code! It was Teh Epic Fail! crowd that blew it up into this huge ZOMG!!1! issue.
Deprecating code does not imply that Oracle will take over. You guys are making it really hard to have an adult discussion. Go beat up on Flash or something
Also worth noting that Java SE 6 update 22 was only officially released Oct 12, so Apple was only a week behind with their release.
Given that they plan to continue support on Leopard and Snow Leopard, I'm guessing this means no work on Java 7 and no Java support planned for OS 10.7.
I was thinking about getting a new Mac, but will have to reconsider. I'm also guessing for roughly OS 10.7-10.8 Apple is planning a iOS style lockdown of the OS. Probably time to jump ship.
Given that they plan to continue support on Leopard and Snow Leopard, I'm guessing this means no work on Java 7 and no Java support planned for OS 10.7.
I was thinking about getting a new Mac, but will have to reconsider. I'm also guessing for roughly OS 10.7-10.8 Apple is planning a iOS style lockdown of the OS. Probably time to jump ship.