Slashdot Log In
Java SE 6 For Mac OS X
Posted by
timothy
on Saturday May 03, @04:11PM
from the hot-x-rated-java dept.
from the hot-x-rated-java dept.
wchatam writes "After a long delay, Apple has finally released a version of Java 6 for OS X. 64-bit Intel Macs are starting to see this pushed out via Software Update, but there has not been an announcement for when 32-bit Intel and PowerPC Mac users will get their versions."
Related Stories
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.

Somewhat old. (Score:2)
I guess it could be a reason which makes it 64-bit only aswell, or they just considered the other platforms to old to care, but that kind of suck. Pretty normal in Apple-land to consider old OS ver
Re: (Score:2)
Re: (Score:2)
I wasn't able to function in OSX with 1gb, so I had to wipe the system and install Ubuntu. Overall, a mac for business was a bad idea since I had a poorly supported, over priced l
Re: (Score:2)
Re: (Score:2)
I've got 4GB of ram in my mac and 1GB in my G4. Both run just fine.
Re: (Score:3, Informative)
Re: (Score:3, Insightful)
Letter of apology (Score:2, Funny)
We're very sorry that unenlightened members of our organization have ported this abomination to your platform. I'm quite sure that you understand that large organizations often have rogue elements working against the organization's best
Re:Letter of apology (Score:5, Insightful)
It's getting really old. At first it was stupidly amusing, now it's just stupid.
Java is a powerful, performant (by far moreso than the current batch of oh-so-trendy interpreted languages), cross-platform, *open-source* set of technologies. This suggests to me that it offers a lot to users of all platforms, especially open-source ones. In fact, it doesn't just suggest this to me. It does offer a lot to users of all platforms, and has been doing so for quite some time now. The fact that Slashdot has now become a playground for groundlessly insulting "Java" in the hopes of scoring a few mod points from the (as usual) hopelessly juvenile Slashdot moderators, makes me sad.
I know it's not trendy to bust into your acerbic sarcasm-filled world with my serious comment here. But somehow I doubt there are many people (aside from a few hard-core
Go poke fun at BASIC or something. Leave Java alone.
Reply to This
Parent
Java6 for Intel 64, and now what? (Score:5, Interesting)
When Apple brought out OS X in 2001, it was all smiles as the system came with free developer tools, a Java-Cocoa API that allowed you to use Java to write native Cocoa apps as well as a C/C++ API that also allowed you to write native Mac apps.
The problem was that the Java-Cocoa api was buggy from the start, apart from having very slow response on a, at the time, very slow user interface. Apple never fixed some of the worst bugs in critical objects (PDF objects for example), and finally, in 2005, dropped further development for the Java-Cocoa bridge altogether.
Last year, Apple dropped further development for the C/C++ API, which is having a major impact on big applications like Adobe's Creative Suite, which now have to move to Apple's in-house Objective-C api.
The overall impression that I get is that Apple is only paying lip service to anything that doesn't come from Apple itself. Apple was known for this in the 90s and there was an acronym for that: NIH -Not Invented Here. This is also Microsoft suffers from, in its Embrace and Extend strategy.
This had serious repurcussions for Apple in the 90s and I, as a long time Mac user worry if it won't happen again. Java6 was available for other platforms over two years ago, and now Java7 is even almost here.
Seriously, if you're a Java developer, is there any actual reason to use Mac OSX? You're far better off using Eclipse on Linux.
Reply to This
Re: (Score:2)
Re:Java6 for Intel 64, and now what? (Score:4, Insightful)
Still, it's what kept Apple form going under in the 90s, so there must be something good about it.
Reply to This
Parent
32 bit intel macs? (Score:2)
What models of macs came with a 32 bit OS? Or are they simply referring to mac os 10.4, which I believe had some 32 bit support, b
Re: (Score:2)
The initial machines were CoreDuo, not Core2Duo. Our family had a 32-bit MacBook Pro, MacBook and Mac Mini. I've since replaced the MacBook Pro with a Core2Duo model, but the MacBook and Mac Mini continue to do
Why isn't this Sun's job? (Score:4, Insightful)
If you're on Linux and you want to run Java apps, you go to the same place and download an RPM.
On Solaris, of course, you go... guess where... and download Java.
Last time I installed it on FreeBSD, I used the Linux binaries in Linus emulation mode. There's a FreeBSD Java project now.
And Sun has recently announced that they'll be supporting Java on the iPhone.
But if you have a Mac, Sun tells you to bugger off and ask Apple.
I'm sure there's some good historical reason for this weird exception, but given that Sun's supporting Java on much smaller platforms than Mac OS X, wouldn't it be in Sun's interest to take on the Mac as well if whatever legacy business agreement with Apple isn't working out? If they did that, then possibly it'd even become possible to get up-to-date Java support for older versions of OS X.
How about it, Sun, are you willing to put your programmers where your mouth is?
Reply to This
Re:No, really, what's Sun up to? (Score:5, Interesting)
At the moment, legal eagles are working through some paperwork regarding acceptance of this code into the GPL source tree. But in coming months we'll hopefully see the BSD and, by extension, Landon Fuller's OS X work hosted in the main openjdk codebase. Patience...
Now on the other matter, the OS X Java, there have been pleadings from Java developers in the past for Sun to take the reins and do an official port. Particularly a few months ago when Leopard shipped without Java 6.
What makes the port to OS X harder than, say, Linux? Among other things:
* A Cocoa implementation of AWT
* Porting the hotspot virtual machine to PPC
* native libraries, e.g. the Java-Cocoa bridge
These are not trivial tasks they require some expertise of OS X and PowerPC internals. If they were simple to implement, Apple wouldn't be 2 years late. For Sun to replicate these existing features from scratch would take many man years. And for 10%, or thereabouts, of the desktop market they obviously don't see a cost benefit. Would Sun be willing to 'buy back' Apple's source tree and GPL it? Some OS X internals Apple may not wish to expose (IP issues) and like Sun's codebase be encumbered by code they don't own.
Ultimately some of the ball is in Apple's court. They have sought to maintain their own Java port for competitive reasons such as low level OS integration. But what competitive advantage they deem to have when their releases are a full version behind Linux, Solaris and Windows is debatable.
Would Apple publish changes back to openjdk? They seem reluctant to. One benefit:
* PowerPC hotspot - someone else can maintain legacy architecture support for the G4. Who else have a vested interest in openjdk? Redhat, who have signalled intentions to support multiple architectures besides x86. Do Apple and Redhat really compete for the same markets, aside from a few Xserves???
Reply to This
Parent
Don't look for this in 10.4 (Score:3, Insightful)
Frankly I was amazed that Acrobat 8 Professional requires Mac OS 10.4 when it only came out 18 months after 10.4 was released. (But then perhaps Apple was paying Adobe a little bit under the table to help strongarm Mac owners into coughing up their $129 upgrade fee.) And of course Office 2008 requires 10.4 as well.
I have a hard time believing that the OS changes so fundamentally from one version to the next that apps can't be reasonably ported. I guess the only reason legacy versions of Windows enjoy so much support is simply because of the vast amount of market share Microsoft enjoys.
Makes me glad I use a free operating system and free software, still annoying as fuck supporting my users though.
Reply to This
Re: (Score:3, Funny)
"Java: write once, debug everywhere."
Re:So? (Score:5, Insightful)
I was about to say that this matters to the Java Fanbois, in the hope that they would finally get to play with the Java 6 features now that they're supported on the major platforms. "Doesn't run on Mac, must run everywhere" is a very solid argument against moving to Java 6.
As it happens, I must be new here, and I accidentally read the article.
Sadly, a Java 6 app still doesn't run everywhere. According to the Update [apple.com], it'll only run on 64-bit Intel Macs with OSX 10.5.2 installed. If Apple doesn't do something about that fact, this update really doesn't mean much for anyone interested in developing for broad market deployment. This will only affect the tinkerers that happen to be running the latest version of OSX on 64-bit hardware, or developers that are fortunate enough to be able to target an audience that uses modernish technology.
So, nothing to see here unless you're a bleeding-edge Java+Mac fanboi. Granted, that particular market segment has gotten the shaft for far too long. It's good to see at least a small step in the right direction.
Reply to This
Parent
Re: (Score:3, Informative)
Re: (Score:3, Informative)
Re: (Score:3, Informative)
The MacBook, the MacBook Pro, the Mac Mini, and the iMac all shipped with a Core Duo model initially. The only model that didn't is the Mac Pro. Oh, and Xserve....
Re: (Score:2)
Re: (Score:3, Funny)
Re:So? (Score:4, Insightful)
There is a real problem at Apple with Java. Java6 was in beta 2 years ago at Apple, and has only been released in a crippled form for OSX, now. The thing is, Java7 is already on its way for the rest of the world.
Reply to This
Parent