• 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: XCode for Jaguar?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode for Jaguar?


  • Subject: Re: XCode for Jaguar?
  • From: Stéphane Sudre <email@hidden>
  • Date: Sun, 26 Oct 2003 11:10:41 +0100

On dimanche, octobre 26, 2003, at 03:41 AM, Chris Hanson wrote:

On Oct 25, 2003, at 6:57 PM, Stiphane Sudre wrote:
His software is now incompatible with previous OS versions. A big step for backward compatibility. And an interesting question is: is the code faster or slower than before?

That is an interesting question. I suspect the performance is comparable.

And as for incompatibility, if it costs 50% as much to write Panther-only software compared to Jaguar- and Panther-compatible software, for some markets the economics could favor writing Panther-only even if Panther isn't widely adopted at first.

If you can be 100% sure that the target is Panther only, yes, but I'm wondering if this represents a huge percentage of the total market.

I'm wondering whether I should say or not that developing with Panther is currently a nightmare for me compared to Jaguar.

You should say that, and you should be specific about why and in what way it's a nightmare.

Perhaps some of us could help you.

Some examples:

- no backward compatibility for some libraries (libSystemB.dylib to name it) and calls. A C/C++ project compiled on 10.3 might not work on 10.2. You have to target 10.2 and if you have to target 10.2, why not just use 10.2.
- you have to refrain from using some 10.3 specific widgets for compatibility purpose.
- XCode look might be great but I don't like using it. I'm counter productive with XCode, spending lots of time to display the information I want to be displayed. It's reminding me Visual Studio.
- I'm wondering why they are re-organizing the IB palettes with every new Dev Tools release.
- Lack of NSSegmentedControl edition in IB is reminding me of the NSTabView case in early IB releases.
- Increasing backward incompatibilities of nib files
- more and more Cocoa API or methods that look like to be interesting but are not backward compatible. For instance the WebKit related Foundation APIs. You can't be sure WebKit is there on 10.2.

My $0.02
_______________________________________________
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.

  • Follow-Ups:
    • Re: XCode for Jaguar?
      • From: Chris Hanson <email@hidden>
References: 
 >Re: XCode for Jaguar? (From: Chris Hanson <email@hidden>)

  • Prev by Date: XCode forgets to compile some files
  • Next by Date: Project Builder under Panther
  • Previous by thread: Re: XCode for Jaguar?
  • Next by thread: Re: XCode for Jaguar?
  • Index(es):
    • Date
    • Thread