• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Java vs Objetive-C
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Java vs Objetive-C


  • Subject: Re: Java vs Objetive-C
  • From: "Brad O'Hearne" <email@hidden>
  • Date: Sat, 8 May 2004 15:35:50 -0400

Tony,

I don't mean to knock your friend, but String comparison speed does not a programming language make, nor is it the basis alone for a technology decision. Citing pure "speed" (which by the way, means what???) as the determining factor for what is inferior or not is a little ridiculous. By that rationale, we all ought to dump all 3+ generation programming languages, and all be programming in assembly -- nothing "faster" right, I suppose that means its superior?

As a Java developer, I'll be the first one to sing Java's praises. But it has some shortcomings that are just plain difficult to get around, if the problem you are trying to solve requires strength in these areas. I am using Cocoa now because it just doesn't make sense to use Java for my application. Java has some great advantages, but it also has some big holes:

1. Inferior by far on the desktop -- no native GUI technology.
2. No native application interoperability.
3. No direct control over memory management.
4. Automatic array bounds checking is a big performance hit for large array operations with many iterations.
5. The Java Community Process (JCP) seems to lend itself first to influence by large groups of people (companies) rather than first to good ideas. In other words, you nearly have to have the critical mass to bring an idea to complete prototype in order to merely propose it.

I could go on. Some of the above might even be considered an advantage, like the fact that Java manages memory for you, but this is sometimes undesirable doing things like heavy graphics work or gaming software. I think what Apple *should* do is exactly what they are doing: do what is best for the Mac, and open up Mac's native functionality to languages like Java (with Java, they've wrapped Cocoa with JNI wrappers so you can dump things like Swing). Thanks to this effort, Mac is the *only* platform IMHO that even provides a truly competitive GUI technology for the Java platform. Not even Sun has managed to do this on *any* platform.

brado
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Re: Java vs Objetive-C (From: Allan Odgaard <email@hidden>)
 >Re: Java vs Objetive-C (From: Finlay Dobbie <email@hidden>)

  • Prev by Date: Re: Archiving ABPerson - Solution
  • Next by Date: Re[2]: Can a sheet appear at an arbitrary window position?
  • Previous by thread: Re: Java vs Objetive-C
  • Next by thread: Re: Java vs Objetive-C
  • Index(es):
    • Date
    • Thread