upvote
There was a time (around the beginnings of Mac OS X) when Java was considered a first class citizen in Mac OS X, next to Objective-C.

Some NeXT products like WebObjects got ported to Java (and ran not only the iTunes backend but also things like the original Dell online store) and there was something called the Java bridge which allowed you to program Cocoa applications with Java.

https://developer.apple.com/library/archive/documentation/Co...

Oh, and with Yellow Box for Windows, this was also possible on Windows.

If you look at the screenshots here, it's mostly Windows 2000: https://developer.apple.com/library/archive/documentation/Le...

reply
It wasn't just Apple, in the late 90s/early 2000s there was a not insignificant number of folks in business/academia who thought Java would take over the world. Windows XP also shipped with an embedded JVM for running Java apps out of the box at one stage too, just before Microsoft doubled down on c#/.NET.

Along with MacOS X, Apple's Xcode IDE even had native java project support briefly in this era as well.

reply
Yup, this brings back my academia years in 1998, sitting with KDE 1.0 and Java 1.1. It was mostly Java, then Perl as this fabulous scripting/glue language, teeny bit of C and MIPS Assembler for the low level courses.

We didn't touch a fairly esoteric language called Python much. Because we saw the future. Java and IPv6 was about to change everything.

reply
There was even a Microsoft Visual J++ (and later J#).

It was definitely the thing for a while. Although I remember my very first steps with Java and Swing and my primary impression was "this is so slow".

reply
Java really could have taken over the world, and it can be performant, too.

One of the versions of the most popular game in the world is written in Java, and it's quite capable of being very fast.

reply
One only need look at the job postings for Apple to see quite how common Java backend is there.
reply
Yeah I can see that, even when a recruiter contacted me a few years back for a data engineering position, they were looking strictly for experience in JVM-based languages.
reply
> Clojure

Apple should do more of that - they make cool computers, and should use cool languages.

reply
Yeah, I wish they did more Clojure as well. As far as I could tell, it was kind of snuck in about ~12 years ago, and it kind of grew from there.

To be fair, I know people hate on it, but I honestly do kind of think Objective C is kind of a cool language. I think it's ugly but I think the message-passing style semantics are kind of neat.

reply
Adding Smalltalk message passing as an extension to C was very clever and allowed writing very efficient code and dynamic high level UI code in a single language. The semantics were kept clear by the distinctive syntax of message passing. And allowed access to any existing C libraries.
reply
Objective C is neat inasmuch as it managed to add a simple but practical object system to C without all the added baggage of C++. It wasn't without its downsides - in particular, the overhead of a method call was significantly higher than in C++ - but I still appreciate it for its minimalism.
reply
Back in the day, Objective-C was considered a cool hip language, wasn't it?
reply
> entire backend for iTunes (Jingle) was written in Java

Wasn't that because iTunes started out as a NextStep WebObjects application? WebObjects started on Objective C, transitioned to a framework for Java in early 2000's, came to Apple with the Next acquisition.

reply
iCloud is mostly Java (or was, about 10 years ago when I was there)
reply