Live data from Hacker News

Apple deprecates Java

developer.apple.com

201–210 of 277 posts

Re: Apple deprecates Java

#201
post #195

Earlier quoted context omitted.

Why isn't the Mac platform important enough for Oracle to care? Seems to me that maybe it's big enough that Mac should be supported by Oracle. That would be a bit more ideal, get updates when all the platforms get updates.

Even if Oracle supported Macs. Apple made it clear they won't allow Java Apps in the Mac App Store.

So what? The Mac App Store doesn't erase the fact that I can go to http://www.eclipse.org and get eclipse.

Re: Apple deprecates Java

#202
post #6

Earlier quoted context omitted.

There is already a port of OpenJDK: http://landonf.bikemonkey.org/static/soylatte/ Though it's not developed by Oracle employees afaik.

SoyLatte is nothing more than a build of the OpenJDK BSD Port. You can build that yourself.

Not entirely the case. Soylatte is what became the OpenJDK BSD Mac Port. It was granted re-licensing and was merged upstream to OpenJDK.

What this means:

- The Java 6 Java Research License (JRL) binaries are based on Sun's Java 6 JRL releases, which mean they closely mirror the shipping official Java 6. They are also out-of-date and no longer supported. You can only build them using the JRL sources available from Soylatte, and redistribution of code and binaries is limited by the JRL.

- The OpenJDK 6/7 binaries are built from the OpenJDK repository, which is where all the Soylatte and BSD patchset changes were merged. All current development occurs as part of the OpenJDK BSD-Port project, and the code and binaries are fully redistributable.

Re: Apple deprecates Java

#203

Earlier quoted context omitted.

> It mostly means that they can use the libraries without having to open-source Xcode itself. LGPL would be fine for that.

Yeah, but why bother? It's not like Apple has any reason to go LGPL (and actually, now that I looked it up Clang seems to use the same license as LLVM — which makes sense — and that's the University of Illinois/NCSA Open Source License not the 3-clauses BSD, which again makes sense considering LLVM got started at UIUC, so it's not even Apple who decided on the license of the LLVM suite and related tools, they got int…

http://en.wikipedia.org/wiki/University_of_Illinois/NCSA_Ope...

Looks a lot like a 3-clause BSD, but it's a cross between MIT and BSD. The point on LGPL is that if GCC were LGPL, Apple would be able to link it to Xcode.

Re: Apple deprecates Java

#204
Jobs did say at D8 that Apple chooses technologies that are in their Springs and not their Falls. Java has had far to many Falls....

Seriously, Apple does not need Java and I think the market for Java apps has become few and far....

Re: Apple deprecates Java

#206
post #195

Earlier quoted context omitted.

Even if Oracle supported Macs. Apple made it clear they won't allow Java Apps in the Mac App Store.

So what? The Mac App Store doesn't erase the fact that I can go to http://www.eclipse.org and get eclipse.

But I suppose you won't be able to run it on iOSXI

Re: Apple deprecates Java

#207
post #172

Earlier quoted context omitted.

They should care because they sell hardware to people who use those platforms. They will sell less hardware to Java/Scala/Groovy/Clojure/Jython/JRuby/Beanshell programmers this way. The Mac platform is not important enough for Oracle to care. And Java Apps won't be in the App Store.

So what other JVMs can you run on the Mac today? Will Apple open-source their JVM as a starting point for whomever wants to pick up that ball and run with it? How do you develop for Android on a Mac when their JVM finally disappears? I understand Android uses Dalvik, but will you be able to run Eclipse to get to that point?

Your point about Android development may be the reason this move occurred. The IOS vs Android war is at full steam right now and Apple is known to be the aggressor in it thus far.

Re: Apple deprecates Java

#208
post #3

Note that they've only deprecated their own Java runtime .

Yeah I noticed that. Does that mean that Sun can start creating the runtime again? Does that also mean I can skip the hassle of going to Apple Dev center when I want to download the JRE?

Re: Apple deprecates Java

#209
post #69

Earlier quoted context omitted.

I think "may be removed from future versions of Mac OS X" sounds pretty much like it is very likely that it will be removed.

I don't think so. It makes it sound like if that's ever a bother, they'll drop it. But right now, they probably have the deployment architecture so no reason to ever remove it. On the other hand, don't hold your breath for an OpenJDK release from Apple. In fact, that's very likely the purpose of the move: they're warning developers they will not port Java 7.

And it's a suggestion to people who rely on Java being there that they should keep a copy of the installer package handy, because it might not be included later.

Re: Apple deprecates Java

#210
post #144

Earlier quoted context omitted.

It used to be cross platform. Back in the dotcom days, I was at a company that would sell implementations of it for Windows and Sun servers. That was when the software price started at 50k (iirc) though. When you're charging that kind of coin, I guess the motivation to support Windows is higher.

Java has never been cross platform. Back in the dot.bomb days running java on anything other than Windows and Solaris was a huge pain in the ass when not outright impossible, and there was Sun's infamous internal memo about how much Java on Solaris sucked!

I found the memo from 2003: http://web.archive.org/web/20030210024427/http://www.interna... -- this blog thread discussing it is enlightening: http://www.advogato.org/article/624.html
Post reply on HN