• 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: ObjC in time-critical parts of the code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ObjC in time-critical parts of the code


  • Subject: Re: ObjC in time-critical parts of the code
  • From: Chris Williams <email@hidden>
  • Date: Sun, 18 Jan 2009 20:11:03 -0800
  • Thread-topic: ObjC in time-critical parts of the code

In 25 years in the computer business, I've seen precisely one example of
someone successfully re-coding around performance issues with the language
or library.  And that was only because they coded a tiny snippet of
assembler that managed to fit into the pre-fetch cache of an 80286.  Every
other time, the effort would've been far better spent avoiding unnecessary
calls and work in their own design than wasting time fighting or rewriting
the language/library.

> From: Justin Carlson <email@hidden>
>
> Optimization is learned, and it takes time to learn.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: ObjC in time-critical parts of the code (From: Justin Carlson <email@hidden>)

  • Prev by Date: Re: ObjC in time-critical parts of the code
  • Next by Date: Memory allocation issues with NSObject and NSString
  • Previous by thread: Re: ObjC in time-critical parts of the code
  • Next by thread: Re: ObjC in time-critical parts of the code
  • Index(es):
    • Date
    • Thread