Article:		Mac Technologies Enabled for Java
Subject:		Java vs. Objective C
Date:		2001-05-27 02:48:08
From:		pisej5
While not wanting to instigate another round of programming language wars it should be obvious that Objective C is a problem for Apple as this language is central to development using Cocoa but have almost no followers outside the NextStep community. The realization that developers would not switch to Objective C is generally considered to be one of the reasons that Carbon was developed, to allow C and C++ coded apps to make the transition. But Apple need something with a run-time model like Objective C and Java fills this slot. So, noticing that WebObjects 5 now also has a Java interface I would say that Apple is going full steam ahead towards substituting Java for Objective C.

Showing messages 1 through 2 of 2.

• Java vs. Objective C
  2001-05-27 08:57:20  Derrick Story | [Reply | View]
  
  
  Indeed Apple has made a tremendous commitment to incorporating the Java Framework in to Mac OS X. And I know from my discussions with them that they are very, very, excited about the prospects of Mac OS X becoming a primary Java development platform.
  
  That being said, my impression is there's lots of excitment around Objective-C too. And I don't see it becoming an "either - or" situation any time soon.
  
  I think one of the reasons that I'm so interested in Mac OS X is that there's Java, Objective-C, and Unix ... all in one beautiful install.
• Java vs. Objective C
  2001-05-28 01:30:39  laird [Reply | View]
  
  
  Just to elaborate a bit, Apple came to the same conclusions a few years ago, and you can currently write Cocoa applications in either Java or Objective C.
  
  I agree, though that Carbon remains the API if you want to code in C/C++ (or Object Pascal).
  
  BTW, TrollTech just ported QT to MacOS X, which I believe means that any KDE application ought to easily recompile for MacOS X. I haven't tried it myself, yet, but the demo's look great.