• 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: Allocating too much memory kills my App rather than returning NULL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Allocating too much memory kills my App rather than returning NULL


  • Subject: Re: Allocating too much memory kills my App rather than returning NULL
  • From: Don Quixote de la Mancha <email@hidden>
  • Date: Tue, 08 Nov 2011 22:56:08 -0800

On Tue, Nov 8, 2011 at 10:49 PM, Kyle Sluder <email@hidden> wrote:
> On Tue, Nov 8, 2011 at 10:44 PM, Don Quixote de la Mancha
> <email@hidden> wrote:
>> Kids These Days.
>>
>> While the Space Shuttle exploded twice, I hasten to point out that
>> neither of those failures was due to software bugs.
>
> The Shuttle's software was a closed real-time system written entirely
> by one team within NASA that followed incredibly strict code-auditing
> and development procedures. We studied it in college.
>
> If you tried to follow the NASA's development methodology, your
> competitors would eat your breakfast, lunch, and dinner before you
> shipped v1.0.

That's the problem I'm trying to fix by demonstrating that software
doesn't have to crash.

The reason competitors eat the lunch of careful coders is that
end-users are conditioned to expect that their products will be
unreliable.  That's why just about all software comes with End User
License Agreements that disclaim any warranty, and end-users have come
to just expect that all manner of malware will screw up their
computers on a regular basis.

Apple's strict control over what can be installed on iOS devices makes
this less of a problem, but it does not elimate it.  Consider that
Mobile Safari has no way to revoke trust in SSL certificates, for
example.  Also, while App crashes are cause to be rejected from the
App Store, I've downloaded a few that have 100% reproducible crashes.
Even Apple's own Apps as well as the iOS itself crashes on a regular
basis.

It REALLY does not have to be that way!


--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
email@hidden
_______________________________________________

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

  • Follow-Ups:
    • Re: Allocating too much memory kills my App rather than returning NULL
      • From: Greg Parker <email@hidden>
References: 
 >Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Jens Alfke <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Greg Parker <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Wade Tregaskis <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Joar Wingfors <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Wade Tregaskis <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Kyle Sluder <email@hidden>)

  • Prev by Date: Re: Allocating too much memory kills my App rather than returning NULL
  • Next by Date: Re: NSFileHandle readInBackground vs threading?
  • Previous by thread: Re: Allocating too much memory kills my App rather than returning NULL
  • Next by thread: Re: Allocating too much memory kills my App rather than returning NULL
  • Index(es):
    • Date
    • Thread