( and frankly, why on earth would you need constant updates for java now? I haven't updated my java runtime in like 3-4 years on my PCs )
I totally agree, almost all my software is AT LEAST four years old, I wouldn't want it any other way!
( and frankly, why on earth would you need constant updates for java now? I haven't updated my java runtime in like 3-4 years on my PCs )
I enjoy that people are still voting this as negative. Oracle isn't going to let Java rot on the OS X platform.
Larry is ripe for picking because he wants to make his company like Apple and has a load of debt.
I just checked the Oracle website. Their latest announcement (September 20, 2010) regarding Java, under the headline "Oracle Outlines Plans for Java Platform" states that:
"... Oracle is advancing the Java platform and optimizing it for new application models and hardware ..."
The press-release doesn't mention OS X. But it sure could be a part of the road map. Read the entire Oracle press-release here:
http://www.oracle.com/us/corporate/press/173712
Since IBM has given it's support to OpenJDK chances are this is what most Java devs are going to use (transition has started in the linux community), I believe you can already compile OpenJDK on mac os x.
So for those that use Java it shouldn't be a big deal at the arrival of Lion.
There's 2 problems with this.
1) Business customers will not get any comfort from "this might not be the best way to do it". What they want is certainty that they can spend money on pro-level mac hardware for their software development teams and it's not a wasted investment. Until there is certainty them - for sure - those purchases will be on hold.
2) There's this assumption that because OS X is bigger now, Oracle will jump in and support it directly. Ain't neccesarily so. Consider: Java is mostly prevalent in the server space - and Oracle has a big linux investment, so JVM on linux makes sense. By covering that and Windows, they give a huge set of platform coverage for the development side. Now, consider - if Oracle don't support OS X - how much money are they going to loose? I'd say 0. It is *far* more likely that enterprises will change their hardware platform away from the Mac than they suddenly stop writing Java. Why would oracle spend time and money on a port when all they need to do is wait; Java users have to have a supported development environment so they're forced back to Windows / Linux.
Java application haters just don't get it. A huge amount of software development targets Java, only a tiny fraction of it is used by consumers. Those guys need computers, they liked OS X because it's got good java support, UNIX, and a nice GUI. There's been a huge uptick in macbook toting IT people, who then were a great ready audience for writing iPhone apps because they had the kit. They don't care what the app store rules are, they don't even care if Java is an OS component or a separate download; or even who supplies it - just the assurance that it is there and supported. An no, some shonky Soylatte build on X11 isn't going to cut it.
Also, you may be surprised what consumer stuff IS java. Flash builder; eclipse IDE. Moneydance personal finance; Java. PS3 media server; Java. Many language development environments are eclipse, and therefore java, based.
No JVM = No OS X = No enterprise apple sales.
Would you bet your house / business on that assertion?
Macs have cemented their place in the computer world, particularly developers. Oracle will not be able to ignore the Mac. I'm sure that is what Apple is counting on.
sicn said:Very interesting indeed. Unless Oracle will release a JDK for Mac this may mean that I know 200+ software developers (no kidding, my company) that will ditch the Mac and buy another machine because the tiny 2000$ Mac investment that we "threw out of the window" is NOTHING in comparison to the millions of dollars invested in building mission-critical Java Systems for us and our clients.
I actually believe that this announcement could play a much bigger roll in abandoning the Mac than many other previous announcements (like the totally locked down Mac App Store) because I hardly know anybody that did not buy the Mac as a result of wanting a nice Unix-like system for software development. And keep in mind, Objective C is only a program language for fart apps, it's not for real world business and web-scale software.
First the use of Java in the enterprise is dying off. In your case you are into it up to your neck and can not see what is happening around you.
Oracle, this is time to shine on the Mac. Please do't screw it up like Adobe did; otherwise, well the consequences for Adobe now are clear.
Before anyone gets the wrong idea -- as a developer it is vital to me for Java to remain supported in OS X, as I do have to use it for certain stuff.Still, this doesn't answer why Java is BARRED FROM THE APP STORE (both iOS and OS X). I've used many great Java programs that are fast and well-integrated into OS X. Poker Copilot comes to mind.
One thing about this thread that bothers me is the often raised business angle. I'm going to be perfectly blunt here but if your business has been tied to Java for years you need to look at your management team. It is simply a poor choice in my mind to choose Java over standardized languages. Frankly this is a good example of why.
Being a version behind isn't really a bad thing. He should just look at it like everyone else is testing updates in the real world.
New unknown security bugs could be exploited while OS X wouldn't be affected because it would be on a previous build.
- YAY for not being on the bleeding edge
...
When OS X launched, it had three major APIs. They were considered co-equals.
1. Carbon - The refined API of the "Classic" Mac OS, bumped for OS X. It was possible to create a Carbon app that would run one binary in both OS 9 and OS X. (See AppleWorks.)
...
First Apple tossed Carbon aside, now tossing Java aside
....
While that may have been true in the past, Steve does not have his facts straight.Jobs' reply was:
Sun (now Oracle) supplies Java for all other platforms. They have their own release schedules, which are almost always different than ours, so the Java we ship is always a version behind. This may not be the best way to do it.
Minor correction on your correction.It is UNIX, no Unix or unix and OS X is only compliant since 10.5 Leopard, en then only when running on Intel hardware. Older versions or those running on PPC are not.
Side-note: compliant versions of OS X are, together with Solaris and HP/UX, the only systems compliant with the latest UNIX specification (SUS3).
I fully supported Apples stance on Flash, but as a Web Dev I can't stand behind this. Java is still in use by tons and tons of different companies. Phasing it out will only force developers to switch to PCs to simply work on things. Not good.