Women in Technology

Hear us Roar



Article:
  Building Cocoa-Java Apps with Eclipse
Subject:   Great article
Date:   2005-04-23 03:19:57
From:   helgegrimm
One of the best articles that I've read on Macdevcenter. I would never have tried that myself. Thanks!
Full Threads Oldest First

Showing messages 1 through 4 of 4.

  • Great article
    2005-04-23 21:01:26  bfancher [View]

    Eclipse is a great tool, but the real question isn't how do I use it for writing Cocoa-Java apps, but why on earth anyone would use Java for writing a Cocoa application, when Cocoa's native language of Objective-C is vastly superior? Is it because you want to your program to run slower (thanks to the Objective-C to Java bridge)? Maybe you want it to be harder to read (because of Java's idiotic unnamed method arguments)? Or is it that you just like having typecasts littered all through your code like rodent turds?
    • Great article
      2005-04-24 09:30:43  ebelin [View]

      Sounds like a die-hard bigotry to me. One might want to use Java to write any ( including Cocoa ) app becuase of the tools available. I've seen a lot and I have to say that Eclipse ( along with IDEaJ, from where Eclipse "borrows" many features ) has simply the best ( overall in industry ):

      1. debugger
      2. code assist
      3. code navigation and search
      4. code refactoring
      5. interface to CVS ( via SSH )
      6. Java has obligotary exception handling ( missed exceptions are caught at compile time )
      7. Background compilation
      8. Many other things that take mundane parts out of everyday programming away.
      9. Oh, and hey, real grabage collection, for a change

      This is a few why's. Now, you maybe a super-programmer and do not use any of those things, but some of us are "normal" people and every once in a while ( heck, every day, actually ) use all of those features.

      I feel sorry for people like yourself. Languages do not matter anymore - libraries do. It takes about 2 hours to grasp Objective-C ( language ) and even write leak-free code. It takes much longer to learn the guts of Cocoa libraries and how to use them.

      Not to say that Java is perfect though. Microsoft realized the shortcomings of Java and created JavaNT *cough*.NET*cough*. At the moment they are lacking in the tool department too. As soon as they catch up - we will have even more choice.

      Remember, no tool ( language ) is perfect for all jobs. And every tool ( language ) is perfect for some job. I am not going to participate in this discussion. I have figured most things for myself, so this is just a note to folks who might be misguided by the "shored" commentors.

      Interesting article, by the way. For one, I would have never tried it myself. It is a pity that Apple does not embrace Eclipse as the "IDE of choice for MacOSX" and does not adopt Objective-C to be well supported in that great IDE. If they did, they would have passed Microsoft in developer convenince for a couple of years, which is quite a lot...
      • Great article
        2005-04-24 13:19:12  otto [View]

        It is a pity that Apple does not embrace Eclipse as the "IDE of choice for MacOSX"

        I agree. The first step would have to be improving Eclipse's performance on OS X.

        and does not adopt Objective-C to be well supported in that great IDE

        Well, as much as Xcode is a Obj-C IDE at heart, Eclipse is a Java IDE through and through.

        I'd love to have a IDE that handles all languages well, but it sounds too much like a silver bullet to be true.
    • Great article
      2005-04-24 09:29:52  ebelin [View]

      Sounds like a die-hard bigotry to me. One might want to use Java to write any ( including Cocoa ) app becuase of the tools available. I've seen a lot and I have to say that Eclipse ( along with IDEaJ, from where Eclipse "borrows" many features ) has simply the best ( overall in industry ):

      1. debugger
      2. code assist
      3. code navigation and search
      4. code refactoring
      5. interface to CVS ( via SSH )
      6. Java has obligotary exception handling ( missed exceptions are caught at compile time )
      7. Background compilation
      8. Many other things that take mundane parts out of everyday programming away.
      9. Oh, and hey, real grabage collection, for a change

      This is a few why's. Now, you maybe a super-programmer and do not use any of those things, but some of us are "normal" people and every once in a while ( heck, every day, actually ) use all of those features.

      I feel sorry for people like yourself. Languages do not matter anymore - libraries do. It takes about 2 hours to grasp Objective-C ( language ) and even write leak-free code. It takes much longer to learn the guts of Cocoa libraries and how to use them.

      Not to say that Java is perfect though. Microsoft realized the shortcomings of Java and created JavaNT *cough*.NET*cough*. At the moment they are lacking in the tool department too. As soon as they catch up - we will have even more choice.

      Remember, no tool ( language ) is perfect for all jobs. And every tool ( language ) is perfect for some job. I am not going to participate in this discussion. I have figured most things for myself, so this is just a note to folks who might be misguided by the "shored" commentors.

      Interesting article, by the way. For one, I would have never tried it myself. It is a pity that Apple does not embrace Eclipse as the "IDE of choice for MacOSX" and does not adopt Objective-C to be well supported in that great IDE. If they did, they would have passed Microsoft in developer convenince for a couple of years, which is quite a lot...