Re: Exiting non-POSIX threads?
Re: Exiting non-POSIX threads?
- Subject: Re: Exiting non-POSIX threads?
- From: Fritz Anderson <email@hidden>
- Date: Wed, 31 Jul 2013 09:45:53 -0500
On 31 Jul 2013, at 9:23 AM, Oleg Krupnov <email@hidden> wrote:
>> Which is why he specifically mentioned the option of an external watchdog process.
>
> This seems like an overkill. Every app needs some kind of crash
> reporting, are you suggesting to accompany each app with a watchdog
> process? Besides, the user might think your app is a spyware when he
> sees the watchdog process in Activity Monitor.
Yes.
It has these advantages:
• It the practice of almost every high-end third-party developer I've encountered. Perhaps I am biased by my opinion that applications are high-end if they adopt this practice.
• It assures the user that the developer will receive the report. I have no such faith in Apple's crash reporter.
It has these defenses:
• By definition, the best way to do a job is not "overkill," a term that isn't to be confused with "more work for the developer."
• People don't run ps(1) or Activity Monitor. Those who do see dozens of processes they can't identify. Those who pass that threshold know enough to look for the parent process (your application). Those who can't do that, and kill it, deserve what they get; they haven't lost any of the functionality they expect.
• A small, sleeping process consumes practically no resources. There is no cause for horror.
— F
_______________________________________________
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